Sascha Vujevic created MNG-5547:
-----------------------------------
Summary: import scope of dependencyManagement doesn't seem to work
Key: MNG-5547
URL: https://jira.codehaus.org/browse/MNG-5547
Project: Maven 2 & 3
Issue Type: Bug
Components: Dependencies, POM
Affects Versions: 3.1.0
Reporter: Sascha Vujevic
Attachments: build.log, client.zip, parentone.zip, parenttwo.zip
In the example are two parent-projects of type pom. Both have different
versions of log4j in the dependencyManagement.
If a client uses one of the parent-projects as parent and the other one to make
an import-scope in the dependencyManagement the effect is that the
log4j-version of the parent-pom will be used instead the version of the
import-scope.
Maybe this behaviour has changed to former versions. Then how can i achieve to
get the log4j-version of an import ?
Thank you for your help and suport.
Best regards
Sascha
--
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
