Hi Dave, javadevd...@googlemail.com wrote at Freitag, 4. September 2009 10:53:
> there is no picture? I added it to the first mail.. and i can see it as an > attachment... I try it again with that mail... Maybe you did not realize yet, that versions defined in a depMgmt section do always take precedence - even for transitive deps! > I already use Maven for complete Version Management. > >>Use in this global POM a dependencyMgmt section and define there >>all your deps with fix versions. > > And here is the problem. This is not possible because the problem I > described is a transitive dependency, I don't know! (Because its in any > dependency of another dependency...) So defining fix versions of the > "first"-direct dependency is ok (DEP_A). But if there are dependencies in > DEP_A (DEP_A->DEP_B) and DEP_B has some dependeny with open version-ranges > (DEP_Copen)... > then I cant influence this. And there is suddenly a new version of the > dependency (DEP_Copen) used by all versions of my project (V3,V4 etc.).. > and then there can be unpredictable bugs... (in an older tested version of > my project) > > I think the picture is very important to understand this use case, so I > add it again... That's the whole point, the problem you describe in your use case does not exist in this way. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org