• code: https://github.com/watson-developer-cloud/java-sdk
• maven: http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22java-sdk%22

We use Sonatype as repository manager, it's used as the input channel for the Central Repository running the Sonatype Open Source Repository Hosting(OSSRH) service.

If you are not familiar with Sonatype and/or the maven release process please read the following material:

• Sonatype: http://central.sonatype.org/pages/apache-maven.html
• Releasing artifacts to Sonatype: http://kirang89.github.io/blog/2013/01/20/uploading-your-jar-to-maven-central/
• Install GPG, and create a public key. More info: http://central.sonatype.org/pages/working-with-pgp-signatures.html

1. Update all READMEs to include the new version number

   This can be done using bumpversion. If necessary, it can be installed with the following command:

   pip install bumpversion

   To then update all version numbers, simply run:

   bumpversion major|minor|patch

2. Perform a release deployment to OSSRH (Staging) with:

   `gradle release`

   You will have to answer prompts for versions and tags. That will tag and commit a new version into your repository automatically.

The above steps should work, but we've run into situations where the archive uploading through CI has failed because IP changes caused multiple staging repositories to be created in Sonatype, each with different pieces of the full set of artifacts. If this happens, the repositories won't be able to be closed and released on the Sonatype website.

Uploading the archives locally with the following command solves this problem:

./gradlew uploadArchives -Psigning.keyId=<keyId> -Psigning.password=<keyPassword> -Psigning.secretKeyRingFile=<pathToKeyRingFile> -PossrhUsername=<sonatypeUsername> -PossrhPassword=<sonatypePassword>

The arguments should be populated with the following:

• -Psigning.keyId: The ID of your public key you created after following the link in the prerequisites
• -Psigning.password: Your password you created for making public GPG keys
• -Psigning.secretKeyRingFile: After creating your public key, you create your keyring file with the following command and use the absolute path to your new file:

gpg --export-secret-keys -o <outputFilename>.gpg

• -PossrhUsername: Your Sonatype username
• -PossrhPassword: Your Sonatype password

Assuming this command works properly, you should be able to then log into Sonatype and close and release the repository as usual.