Deploy to Maven central repository

[bclozel]

Ready to work on this! See this issue for some details.

[bclozel]

https://oss.sonatype.org/content/repositories/snapshots/org/resthub/ 2.0-SNAPSHOT published on sonatype.

[bclozel]

Looks like maven-releasing a project with windows, git, github, gpg is not the easiest task. The following links explain how to achieve this:

• http://www.theroundmeatball.com/making-maven-release-plugin-on-windows-with-git-gpg-and-github-to-work/
• http://www.sonatype.com/people/2009/09/maven-tips-and-tricks-using-github/

So you have to use a SSH connection to git@github.com, because maven-release-plugin can't display password prompts. Basically, the Sonatype user guide says so for svn.

Doing so behind a company web proxy is a pretty bad idea, especially if it caches 404 HTTP responses, thus preventing you from properly pushing artifacts on a remote nexus. Also, you need to be allowed port 22 on a remote host, otherwise you won't be able to use the git@github connection.

Fun times.

[sdeleuze]

Ouch ! Perhaps we should stay with the semi manual mvn versions:set and not mvn release in order to at least just use github http connection ?

[bclozel]

Probably. But we'd have to manually sign (oh boy) and deploy artifacts (easy with the web interface).

[bclozel]

It is actually doable manually:

• release with versions-maven-plugin
• commit, tag and push
• create and sign artifacts (one-liner)
• create a JAR bundle containing all these artifacts (one-liner)
• manually upload using Sonatype web interface

[bclozel]

The full automatic maven-release works with a bit of extra configuration.