Prepare project for Maven Central release about caesar HOT 9 CLOSED

Created new ticket at Sonatype JIRA: https://issues.sonatype.org/browse/OSSRH-59936

from caesar.

Running

mvn clean compile

now only uses the module path during compilation.

from caesar.

Running

mvn install

now successfully generates the javadocs in target/apidocs, thanks to this post.

from caesar.

Added Sonatype credentials to Travis

from caesar.

Look into gpg key generation!

from caesar.

Move BinaryString and Identity to an internal package; keep them module-private.

from caesar.

Project can now successfully be deployed Sonatype snapshot repo by running:

# set environment variables 'SONATYPE_PASSWORD' and 'SONATYPE_PASSWORD'
mvn deploy -P publish -DskipTests=true --settings ".travis/maven-settings.xml"

from caesar.

Release new version like so:

mvn release:prepare release:perform

Also, look into the specific plugin options. We might want to set the releaseVersion manually.

Typical workflow:

• do some work on the branch
• at some point, decide whether you've done enough work for a new major, minor or patch release
• tag the version with a Sermver <TAG_NUMBER>, run the plugin and push changes to remote repo:

mvn --batch-mode release:prepare -DreleaseVersion=<TAG_NUMBER>

from caesar.

Fix keys. Read this: https://maven.apache.org/developers/release/pmc-gpg-keys.html

from caesar.