Hi Dave, javadevd...@googlemail.com wrote at Freitag, 4. September 2009 12:10:
> sorry, that i'm so annoying ;-) Hehehe .. >>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. > > U say, that this use case will neber happen? So Maven ignores version > Range from DEP_B:2.3 to DEP_C ? No, because DEP_C has not been fixed in fist place. > If this is right, than thanks for all the comments ;-) And the my use case > is really impossible... Rule of thumb: All dependencies that end up somewhere in a war, ear or assembly should have been locked down in the project's global POM. As Stephen already suggested, use dependency:tree to get the current versions in use. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org