This page attempts to explain the process used for releasing SeedStack Java components. They are released on Maven Central through oss.jfrog.org (OJO) and Bintray. You need to have release rights in Bintray SeedStack organization and a sonatype account with publication rights to the org.seedstack group.

All Travis CI builds are automatically published to pushed to OJO. You can find any published build in the builds section. From there you can promote any snapshot build to a release. Be sure to only promote a build that satisfies the following conditions:

• No SNAPSHOT dependency left,
• All the commits you want to release are present.

To promote the build issue the following REST call:

curl -X POST -u user:bintrayApiKey http://oss.jfrog.org/api/plugins/build/promote/snapshotsToBintray/{:packageName}/{:buildId}

You will notice a success message if everything's ok.

For posterity, you must tag the commit hash you just released with the corresponding semantic versioning tag. For instance create a tag named v2.1.0 for version 2.1.0.

You must update the source code with the next development version. For instance, to set the new development vesion to 2.1.1-SNAPSHOT:

mvn versions:set -DnewVersion=2.1.1-SNAPSHOT

If everythings ok, commit the modifications:

mvn versions:commit
git commit -a -m "Update to next development version 2.1.1-SNAPSHOT"

Push the commit.

The promoted build is automatically pushed from OJO to Bintray. From there, you can sync the release to Maven Central. Go to the corresponding package, on the just released version. Click on the Maven Central tab, enter your Sonatype credentials and click Sync. If you want to inspect the package on Sonatype before it hits Maven Central, uncheck the "Close and release repository when done" checkbox.