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>
[maven-release-plugin] prepare release pom-0.9
[maven-release-plugin] prepare for next development iteration
Exposed a Maven repository under the URL of the build.

This makes it easier to access the Maven repository from a build, and
generally make the URL strucure more consistent with the rest of
Jenkins. Concrete benefits include taking advantages of permalinks
(and thus other plugins that produce permalinks, such as the promoted
builds plugin.)

The TransientBuildActionFactory extension point was introduced in 1.459,
but in that version it is broken. 1.466 was picked as the base version
because it's the release used for LTS.
Merge pull request #9 from kohsuke/master

Exposed a Maven repository under the URL of the build.
Fixing the build problem.

ClassNotFoundError: MojoNotFoundException was because Maven decided to
pick up 2.0 of maven-plugin-api (which is specified in
jenkins-maven-plugin), over 3.0 of maven-plugin-api (which is specified
in the core) because the former is shorter from the root.

I then had a Groovy <-> GMaven version issue. I fixed this by defining
Groovy as a dependency in gmaven plugin. IIRC, GMaven plugin relies on
the project to have a compile/runtime dependency on Groovy, and when
that doesn't have the right version it dies with NoSuchMethodError.

And finally GMaven complained about missing Ant, so that was added too.
Merge pull request #10 from kohsuke/master

Fixed a build problem induced by my previous change.
Change the repositories to the newer jenkins-ci ones.

Signed-off-by: Nigel Magnay <nigel.magnay@gmail.com>
Update some dependencies to newer versions.

Signed-off-by: Nigel Magnay <nigel.magnay@gmail.com>
If the SHA1 id happens to be prepended with more than one zero,
we were not creating the correct ID.


Signed-off-by: Nigel Magnay <nigel.magnay@gmail.com>
Use File in copy so that it ought to work on Windows.
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release pom-0.11
[maven-release-plugin] prepare for next development iteration
[FIXED JENKINS-15714] HTTP 500 Internal Exception accessing Maven Repository URL for specific builds

The code attempted to modify a read-only view returned by Guava collections utilities. Modified it to use filtering instead.