-SNAPSHOT is newer, which is strange. How is this supposed to work?
That makes sense to me. Maven thinks -INTERNAL is a *fixed* version.
It's no different than 1.2 or 1.3-beta. It's just some version,
deployed at some point in the past. The -SNAPSHOT version is "the
latest".
If you read
http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins, it says
"Set the version to be -INTERNAL instead of -SNAPSHOT". Thre si not about
version number increase and the plugins usually are snapshots. So if
snapshot is published, the -INTERNAL will not be used. It doesn't make sense
to me.
The reason to change SNAPSHOT into another string, like INTERNAL, or FOOBAR,
comes from the fact that when you mvn install a SNAPSHOT version, and somebody
deploys a new snapshot to a remote repo, then that latter version will be
downloaded
and considered newer. This used to be not the case.
To be completely safe, you should specify the -INTERNAL version in the root pom
in a pluginManagement section.
So you specify a fixed version, and by using that 'INTERNAL' string, you're safe
from new releases. So even if the -INTERNAL is considered newer than -SNAPSHOT,
you're still going to get updates if the actual version changes:
Say you modify 2.1-SNAPSHOT and deploy as 2.1-INTERNAL. Then when 2.1 or any
newer
version is released, that newer version will be used. Depending on wheter you
want
to lift with new releases you decide wheter to set the version in a
pluginManagement
section or not.
On the other hand you could also just deploy the snapshot and specify the fixed
timestamp
version in the root pom.
-- Kenney
Thanks, Jan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
