publish version 1.0.0 to Maven Central

[mbjones]

The library would be more accessible from a common, public maven repo. Publish it there.

[mbjones]

While publishing to Maven Central would be great, the library can easily by deployed from source here from GitHub. So, we have not prioritized the maven release, even though the ezid library is in active use across man repositories, including the KNB and Arctic Data Center. If a community member wants to help maintain the library, prepare/document it for release to Maven, and maintain it once released, we would love the help. Otherwise, we'll probably just continue to make it available through GitHub here as a source build.

[amoeba]

Some CI solutions allow distributing build artifacts at the end of the build job (we do this for mdqengine/mdqwebapp to get the WAR). If that'd be useful I could enable that here in order produce a JAR for end-users.

[mbjones]

That would be useful, but the bigger issue is getting everything up to standards before submitting, particularly the Javadoc. Standards are outlined here:

http://central.sonatype.org/pages/requirements.html

Its not that much, but we just haven't had cycles to check through it all. Probably worth it though.