On May 14, 2009, at 9:18 PM, Christian Schulte wrote:
Why? In SCM there should never be a non-snapshot module with snapshot
dependencies. Further a non-snapshot module should not be modified
except
for pom.xml
/trunk at revision 4
+root(1.2-SNAPSHOT)
+A(1.0)
+B(1.3-SNAPSHOT)
If the pom of A(1.0) inherits from root(1.2-SNAPSHOT) and
root(1.2-SNAPSHOT) declares a dependency management with snapshot
versions and A(1.0) declares a dependency without an explicit version,
than A(1.0) may start depending on a snapshot. If you do 'mvn
deploy' at
root(1.2-SNAPSHOT) then A(1.0) will be deployed to the release
repository, everything else to the snapshot repository.
Which is exactly why the deploy plugin should never redeploy something
that is already in a release repository. It is ALWAYS wrong, even in a
scenario where you rely on the release plugin to do its magic.
Actually, in the case above since the parent pom is a SNAPSHOT the
deploy should just ignore any modules that aren't snapshots.
OK. So you would NOT mind if maven adds some new features that
are compatible to older versions of maven.
They just shouldn't change things significantly without good
arguments.
Which are only the ones you agree with?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
