Conflict resolution does not pick sub tree of nearest dependency if farther
conflicting dependency has wider scope
------------------------------------------------------------------------------------------------------------------
Key: MNG-4800
URL: http://jira.codehaus.org/browse/MNG-4800
Project: Maven 2 & 3
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.2.1, 2.0.11
Reporter: Benjamin Bentmann
This is a follow-up for the observations made in MNG-4761 and MNG-4790 where
scope widening during conflict resolution will cause inconsistent sub trees in
the resolved dependency graph. For example the unresolved tree
{noformat}
project
+- a:runtime
| \- c:1:runtime
| \- x:runtime
\- b:compile
\- c:2:compile
\- y:compile
{noformat}
will be resolved to
{noformat}
project
+- a:runtime
\- b:compile
\- c:1:compile
\- y:compile
{noformat}
instead of
{noformat}
project
+- a:runtime
| \- c:1:compile
| \- x:compile
\- b:compile
{noformat}
Note the difference regarding inclusion of x/y. The latter tree structure is
however successfully resolved when using compile scope for dependency a.
--
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
