Publish artifacts in a Maven repo

[mmazi]

This can be done automatically using Travis.

[mmazi]

Should we do this? If we don't, the users that use Maven (or (probably) Gradle etc.) will be required to build the project themselves, as currently described in the README.

Publishing snapshots in a Maven Repo (Sonatype) can be done automatically by Travis.

Publishing final releases requires:

• a bit of manual work for each release,
• keeping the PGP keys that allow publishing.

[rjnienaber]

Publishing snapshots in a Maven Repo (Sonatype) can be done automatically by Travis.

I think we would have a good start if we did this.

Publishing final releases requires:

a bit of manual work for each release,
keeping the PGP keys that allow publishing.

I think we would need to do this in order to give confidence in the library. We'll try and follow the relevant guides (OSSRH Guide and Releasing the Deployment) and publish a 'release' version once a good level of functionality has been implemented.

[mmazi]

I'll provide some simpler instructions for what needs to be done to publish final releases.

[mmazi]

Some links:

Securely storing sensitive data (eg. passwords, private keys) that Travis can access

A helpful blog post

[mmazi]

A clarification: Sonatype requires non-snapshot releases to be signed etc. (see #26), whereas snapshot builds don't need to meet these requirements. The plan is to publish unsigned snapshots automatically via Travis on every push (still with full javadocs and sources though, see #30), and to only sign final releases (see #31).