Continuus Auchan created MNG-5460:
-------------------------------------
Summary: Transitive dependency with variable scope
Key: MNG-5460
URL: https://jira.codehaus.org/browse/MNG-5460
Project: Maven 2 & 3
Issue Type: Bug
Components: Dependencies
Affects Versions: 3.0
Environment: Windows xp
Reporter: Continuus Auchan
Attachments: myproject.zip
We have a bad transitivity resolution when using variable scopes in our project
hierarchy on maven 3.
The same test on maven 2 gives us a correct behavior.
I've got a pom parent project with 3 modules.
In the parent pom I define :
-a property "myscope" with value "compile"
-a profile "myprofile" with a property "myscope" with value "provided"
The moduleA depends on nothing
The moduleB depends on moduleA with scope equals to myscope
The moduleC depends on moduleB with scope equals provided
When I enter the command "mvn dependency:tree -P myprofile" I've got
{quote}
--- maven-dependency-plugin:2.1:tree (default-cli) @ modB ---
com.mycompany.app:modB:jar:1.0-SNAPSHOT
\- com.mycompany.app:modA:jar:1.0-SNAPSHOT:provided
{quote}
which is OK, but I also have
{quote}
--- maven-dependency-plugin:2.1:tree (default-cli) @ modC ---
com.mycompany.app:modC:jar:1.0-SNAPSHOT
\- com.mycompany.app:modB:jar:1.0-SNAPSHOT:compile
\- com.mycompany.app:modA:jar:1.0-SNAPSHOT:compile
{quote}
where i do not excpect modA to appear.....
You 'll find in attachment the sample project.
Note that the command "mvn dependency:tree" has the correct hehavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
