Some help is available: http://mojo.codehaus.org/versions-maven-plugin/resolve-ranges-mojo.html
Just prior to doing a release, you will do the following: mvn versions:resolve-ranges This will turn all the ranges into the current version (it does not handle transitive... but if you file a JIRA, we can see about adding support in a later release) That will at least help somewhat. Then you use dependency:tree to find any extra transitives, and add those into your dependencyMgnt section... -Stephen 2009/9/4 Ketil Aasarød <ketil.aasa...@gmail.com> > 2009/9/4 javadevd...@googlemail.com <javadevd...@googlemail.com>: > > sorry, that i'm so annoying ;-) > > > >>because this implies that at least one of the "fix" versions must have > been > >>changed. > > > > Thats not right (I think). Example: > > > > My dependency: DEP_A:1.0 > > Dependency of DEP_A => DEP_B:2.3 > > Dependency of DEP_B:2.3 => DEP_C:[1.0,) > > > > My dependency is fixed, and nothing changed. > > Some day, there is a new Version of DEP_C, so DEP_B:2.3 use this new > > version, because the dependency allows newer versions. > > As long as your project depends on A:1.0, B:2.3 and C:1.0 will be > transitive dependencies. If C comes in a new version 1.1, your project > will still get C:1.0 as a transitive dependency. If B wants to use > C:1.1, B will come in a new version, say 2.4 that depends on C:1.1. > The only way for your project to be affected by the release of C:1.1 > is that A has a new release that depends on B:2.4, and your project is > updated to depend on this new version of A. > > Do you understand the picture? > > -ketil > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
