Recreating https://bugtrack.marklogic.com/27634 in github

We currently provide our own manually managed Maven repo http://developer.marklogic.com/maven2. This works for developers to get the right artifacts and dependencies. However, it's problematic in two ways: 1) A developer has to modify her POM with a new repository entry 2) Our artifacts aren't discoverable for those searching the known central repo for MarkLogic tools.

Out-of-the-box, Maven knows about its Central repo http://central.sonatype.org (and a UK mirror). There is a pretty low bar to publishing to the central repo http://central.sonatype.org/pages/requirements.html, most of which we do already. I'd like to propose for 8 that we shoot for publishing here instead of our own repo. We should maintain older versions in our own repo so as not to break any existing code.

• Sources and JavaDocs
• GPG/PGP signatures
• Dependencies
• Project metadata: Name, description, license, SCM URL, etc.

Thinking about the end-to-end development experience, I view this as a hole in the requirements. (I specified distribution via NPM https://www.npmjs.org in the Node client requirements for just this reason.)

This task covers GA major, minor, and patch releases. Distributing snapshots, for EA evaluation for example, is a separate albeit related issue.