Prepare project for Maven Central release

[Glusk]

Setup Travis to deploy the project to Maven Central every time a new git tag is pushed.

Resources:

• https://bpodgursky.com/2019/07/31/using-travisci-to-deploy-to-maven-central-via-git-tagging-aka-death-to-commit-clutter/
• https://www.phillip-kruger.com/post/continuous_integration_to_maven_central/

[Glusk]

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

[Glusk]

Running

mvn clean compile

now only uses the module path during compilation.

[Glusk]

Running

mvn install

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

[Glusk]

Added Sonatype credentials to Travis

[Glusk]

Look into gpg key generation!

[Glusk]

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

[Glusk]

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"

[Glusk]

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>

[Glusk]

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