[
https://issues.apache.org/jira/browse/MNG-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte closed MNG-5547.
----------------------------------
Resolution: Duplicate
Assignee: Christian Schulte
> import scope of dependencyManagement doesn't seem to work
> ---------------------------------------------------------
>
> Key: MNG-5547
> URL: https://issues.apache.org/jira/browse/MNG-5547
> Project: Maven
> Issue Type: Bug
> Components: Dependencies, POM
> Affects Versions: 3.1.0
> Reporter: Sascha Vujevic
> Assignee: Christian Schulte
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
