Publish to maven central repo

[bradleydwyer]

It would be good if this project could be published to the central repo.

I suspect you'll need to change the groupId to make that happen.

[bclozel]

That would be nice.

I'll look into it this week:

• choose a proper groupId - org.pullrequest (open source forge where resthub lives) or com.clozel (domain that I own)
• follow POM requirements for central repo
• clean up configuration (see this guide for details)

[bclozel]

I've been looking into this.

I'm leaning towards this:

• groupId org.resthub (because I'd like it to be pluggable into resthub - without any strong tie/dependency)
• use jenkins+nexus used by resthub.org

With this solution, I can get total control over continuous integration and artifact deployment; this is a public artifact repository you can use in your pom or in your own nexus mirror configuration.

On the other side, maven central gives more "visibility" to the project, but way less control over artifact deployment (sonatype says oss.sonatype => maven central mirroring "can take one business day"... not guaranteed!)

Suggestions?

[bradleydwyer]

My suggestion would be to publish to central. If you don't then it prohibits other projects from publishing to central if they depend on this one, e.g. the springmvc-router-ide.

Non-central repos can also make it harder for organisations to use. At my current workplace our local repo acts as a proxy to central automatically. If we need to access a non-central repo for artifact resolution it involves a (slow) processes to get the non-central repo added to archiva's proxy list.

If you want faster turn-around on snapshot builds, perhaps push them to your own repo @ resthub.org and push releases to central?

[bclozel]

Makes sense. So http://jenkins.pullrequest.org/ + http://nexus.pullrequest.org/ for snapshots and oss.sonatype for releases (thus maven central).

[bclozel]

Ive changed the project's groupId and java package names (that was mandatory - I'm following the official guide).

Basically, we're waiting for this issue to be resolved.

[bradleydwyer]

Are snapshot builds now available on your repo or is there still a bit more work to do?

[bclozel]

Because we need to inherit from oss.sonatype's POM, snapshots will be uploaded to: OSS sonatype snapshot repo. I've uploaded the first one with a manuel "mvn clean deploy".

For "realtime" snapshots, I need to configure Github's hook + oss sonatype configuration on RESThub's CI (a jenkins instance).

[bclozel]

Release 0.6 is available on OSS Sonatype repository and is on its way to maven central (a manual validation by sonatype is required for the first sync to central).

Totally botched the first release (0.5) because of a PGP key problem.

[bclozel]

Published on central!