[
http://jira.codehaus.org/browse/MNG-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87295
]
Jason van Zyl commented on MNG-2794:
------------------------------------
After looking at this specific case, you are doing something that we do not
recommend. If the project you are working has a direct dependency which you
require for compilation then you should be specifying it. I realize something
has changed, but you should be specifying. And the behavior in 2.0.5 is
actually more correct according to our select the nearest strategy. If you
rearrange the dependencies and put the dependency that has a dependency on
commons-collections 3.0 then the builds works fine.
> Transitive dependency resolution differs between 2.0.4 and (future) 2.0.5
> -------------------------------------------------------------------------
>
> Key: MNG-2794
> URL: http://jira.codehaus.org/browse/MNG-2794
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.5
> Reporter: Fabrice BELLINGARD
> Fix For: 2.0.5
>
> Attachments: Test-DependencyResolution.zip
>
>
> Say you have a project that has 3 dependecies A, B and C, amongst which 2 of
> them have a dependency D but with a different version:
> A -> D v2.1
> B -> D v3
> C (has no transitive dependency to D)
> In the project, you call a class that exists in D v3 but not in D v2.1.
> -> If you launch "mvn clean compile" with M2.0.4, the build is successful,
> but not with M2.0.5.
> And the most surprising: if you remove dependency C, then both builds break...
> I attached a test project that reproduces the bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
