[ http://jira.codehaus.org/browse/MNG-1577?page=comments#action_59632 ]
Ralph Goers commented on MNG-1577:
--
Can you provide a link to the original discussion? I just cannot see how this
behavior can be tolerated. Since almost every dependency at ibiblio
[ http://jira.codehaus.org/browse/MNG-1577?page=comments#action_59634 ]
Carlos Sanchez commented on MNG-1577:
-
most projects will end up with multiple versions of the same jars in them.
That's wrong. What can happen is that different projects will use
[ http://jira.codehaus.org/browse/MNG-1577?page=comments#action_59636 ]
Joerg Schaible commented on MNG-1577:
-
This depends. Think of jBoss with its unified classloader and an ear with two
integrated wars. If each war has a dependency with a different
[ http://jira.codehaus.org/browse/MNG-1577?page=comments#action_51499 ]
Brett Porter commented on MNG-1577:
---
I think I agree, as otherwise its just including the dependency falsely to
ensure it is managed - just need to check the original discussion.
[ http://jira.codehaus.org/browse/MNG-1577?page=comments#action_51559 ]
Carlos Sanchez commented on MNG-1577:
-
I think I agree too
dependencyManagent does not work for transient dependencies
---
[ http://jira.codehaus.org/browse/MNG-1577?page=comments#action_51498 ]
Joerg Schaible commented on MNG-1577:
-
Well, with M1 we used entities to ensure global version consistency among
different projects. For M2 the dependencyManagement was presented as
