Manfred Geiler wrote:
On 2/6/07, Paul Spencer <[EMAIL PROTECTED]> wrote:
<snip>
IMHO we should not add a SNAPSHOT dependency until their their is a
change from the released version of the dependency. This will minimize
the number of projects to released. Thus at the end of the release
process, only the following SNAPSHOT dependencies should exist:
See above. There are no officially available non-SNAPSHOT releases for
"maven-project" or "shared" or "core" yet.
In addition the snapshot dependency should not be add until AFTER the
release is cut.
Same problem and additional danger here:
Imagine a developer changes something and forgets to increase the
version number of the artifact from "x.y.z" to "x.y.z-SNAPSHOT". If he
does a mvn install (or a mvn deploy!!!) he will have a total version
chaos in his local repo: He will have local artifacts with version
x.y.z that differ to the official released artifacts with the same
version number!
See description of the maven release plugin [1] for best practice and
to learn how others are doing.
The version of the artifact should be a SNAPSHOT for the above reason.
I am referring to how the artifact is used. As an example, Tomahawk
v1.1.5 will be dependent on maven-project v2.0.5. My comment was related
to Tomahawk v1.1.6-SNAPSHOT. Should it be dependent on maven-project
v2.0.5 or v2.0.6-SNAPSHOT?
--Manfred
[1] http://maven.apache.org/plugins/maven-release-plugin/
Paul Spencer
