The problem with pinned snapshots is that they are not propagated to
mirrors, and so by using one of them in a release we basically
increase the chances that the codeline will not be buildable in the
future. We would need to add the artifacts into the local repository
module to avoid this problem.
Just because we use the explicit timestamp-buildnumber version for
this artifact doesn't mean its not longer a SNAPSHOT, because in
reality it is still a SNAPSHOT, in a transient repository and for all
we know could be removed tomorrow.
I hope that we can give long lives to our release tags, so that
months or years later one could check one out and it would build. If
we allow bits like pinned snapshots into a release we most certainly
cut the build-ability life of the release much shorter.
--jason
On Mar 31, 2007, at 8:10 AM, Dain Sundstrom wrote:
If it works with the latest release we can switch to that;
otherwise IMO a pinned snapshot is fine. It is just a maven plugin
after all.
-dain
On Mar 30, 2007, at 3:46 PM, Jason Dillon wrote:
Anyone know whats up with the xmlbeans-maven-plugin wrt server/
branches/1.2? Its currently using a pinned snapshot. While this
is fine for M/RC releases, its not for officials, since its still
a snapshot and the artifact could be removed tomorrow for all we
know.
We need to get this dependency sorted before we can release 1.2.
It appears this is the only dependency using a pinned snapshot
like this for 1.2, which is good there aren't more of them.
Anyone know?
--jason
