Hi all (and especially Herve, Jason and those who are working on Aether), We are several to hit what we consider to be a bug but myself I don't understand how we did to not see it before. To be short the problem resides in depMgt usage. It is useful only in the project you are building to enforce/lock some versions. If this is in a transitive path of a dep it is unused. For example here is a sample : http://parleys.com/#play/515ef261e4b0cb5a00d98074/chapter34/about The code to test : https://github.com/ndeloof/maven-puzzler/tree/master/3 As far as we don't define the version in the depMgt of the project itself Maven will use the one from dependencies and won't take care of any other depMgt in the transitive path
Vincent Massol also reproduced it at code level here : http://jira.codehaus.org/browse/MNG-5462 If someone could have a look at this issue please. -- ----- Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
