DepB should not use a range, or else you should lock down depC in your parent pom to a fixed version.
if your dependency: dep A has a fixed dependency on depB, then depB cannot change, so you can sigure out all your current dependencies (dependency:tree is your friend) All you do is before you release, you add a depMgnt section locking down the versions to the versions currently displayed using dependency:tree. Now everything is locked down and no new transitive deps can be added 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. > > U say, that this use case will neber happen? So Maven ignores version Range > from DEP_B:2.3 to DEP_C ? > > If this is right, than thanks for all the comments ;-) And the my use case > is really impossible... > > > dave >