This is how is was designed to work. Aether can do anything but the original 
implementation is simply a map of GAs with a version preference. If the GA is 
encountered then its version is overridden. This effectively gives you a target 
platform like mechanism but is intended to be controlled from the final 
application. Maven does not consider depMan at every level in the tree. It's a 
global map controlled from your project and its functionality is very limited 
in scope. You would need to do some relatively sophisticated conflict 
resolution to have every sub graph and its managed dependencies be reconciled 
with every other. Not that it can not be done but this certainly not how 
dependency management is implemented currently. This is not a bug, this is how 
the feature is implemented.

On 2013-04-08, at 8:28 AM, Arnaud Héritier <[email protected]> wrote:

> 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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to