[jira] Created: (MNG-4134) Conflict resolution with scope widening can cause transitive dependencies to be omitted

["Mark Hobson (JIRA)" <ji...@codehaus.org>]

Conflict resolution with scope widening can cause transitive dependencies to be omitted
---------------------------------------------------------------------------------------

                 Key: MNG-4134
                 URL: http://jira.codehaus.org/browse/MNG-4134
             Project: Maven 2
          Issue Type: Bug
          Components: Dependencies
    Affects Versions: 2.1.0
         Environment: Apache Maven 2.1.0 (r755702; 2009-03-18 19:10:27+0000)
Java version: 1.5.0_18
Java home: c:\Program Files (x86)\Java\jdk1.5.0_18\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: "windows xp" version: "5.2" arch: "x86" Family: "windows"
            Reporter: Mark Hobson
         Attachments: test.zip

The attached zip contains the following project hierarchy:

{noformat}p
+- a
|  \- b
|     \- x:2
|        \- y:1
+- c:runtime
|  \- d
|     \- y:2
+- e
   \- x:1{noformat}

The expected resolved dependencies would be:

- test:a:jar:1:compile
- test:b:jar:1:compile
- test:c:jar:1:runtime
- test:d:jar:1:runtime
- test:e:jar:1:compile
- test:x:jar:1:compile
- test:y:jar:2:runtime

But running {{build.sh}} shows that {{test:y}} is omitted entirely.  Note that changing the scope of {{c}} in {{p}} to {{compile}} shows the correct behaviour.



-- 
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