Added support for maven-metadata.xml so that snapshots work with Maven 3.
Cope with artifacts that have been pruned from their builds.
Generate a maven-metadata.xml file for each individual artifact as well.
Generate checksum entries as well, which Maven requires.
Further revamping of snapshot support.

Things were much more complicated than I originally imagined. We need to
provide date-stamped versions of snapshot artifacts for Maven 3, and
non-date-stamped versions of snapshot artifacts for Maven 2, and we need to
provide metadata for the date-stamped versions in a maven-metadata.xml file
inside the versioned artifact directory.

The all-versions metadata file doesn't seem necessary, so I nixed it to keep
things simple.
Merge pull request #1 from samskivert/master

Added support for maven-metadata.xml so that snapshots work with Maven 3.
Fix  (JENKINS-11357) StackOverflowError on repository browsing
Merge pull request #2 from tivv/master

Fix (JENKINS-11357) StackOverflowError on rebository browsing
[maven-release-plugin] prepare release pom-0.7
[maven-release-plugin] prepare for next development iteration
Maven auto selected org.codehaus.groovy.maven:gmaven-plugin version 1.0 unfortunately that version of the plugin seems to be broken.  Building results in a no method found exception boiling up from the plugin.  My experience suggests that this happens when classes are compiled against one version and executed against another.  I know that 1.0-rc-4 and 1.0-rc-5 work.  But since they are release candidates and since I was updating the version anyway I migrated the groupId to org.codehaus.gmaven.  This groupId seems to be the new groupId for the plugin as according to the website the latest version is 1.3.  Maven clean install runs fine on version 1.3.  Relying on test coverage for regression testing
Merge remote-tracking branch 'origin/master' into HEAD
Merge pull request #3 from dodtsair/master

Building locally with maven 3 does not completely work.
Tacking build number onto snapshot versions was casuing problems. Nixed it.
Merge pull request #4 from samskivert/master

Fixed issue with snapshot versions
When generating the maven metadata, you may have >1 artifact
with the same type, but differing classifiers.

Signed-off-by: Nigel Magnay <nigel.magnay@gmail.com>
Some content types ought to know what their mime type is; seems
that ServletContext doesn't always know how to work it out. Probably
OS dependent.

Signed-off-by: Nigel Magnay <nigel.magnay@gmail.com>
[maven-release-plugin] prepare release pom-0.8
[maven-release-plugin] prepare for next development iteration
Don't use the last modified date of the artifact to generate the
snapshot ID, instead use the timestamp of the build. This means that
the POM and JAR artifacts have the same coordinates - the lack
of which was breaking some builds as the POM file was not findable.

Add build number back in, but fix the 'everything' repository to only
show last builds for snapshots in the metadata.

Add checksums for all artifacts, not just for the metadata.


Signed-off-by: Nigel Magnay <nigel.magnay@gmail.com>