[
http://jira.codehaus.org/browse/MNG-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89706
]
Jason van Zyl commented on MNG-2815:
------------------------------------
Can you give me test projects so I can reproduce this?
> Parent POM defined profile dependencyManagement dependency version overrides
> child pom explicit dependency
> ----------------------------------------------------------------------------------------------------------
>
> Key: MNG-2815
> URL: http://jira.codehaus.org/browse/MNG-2815
> Project: Maven 2
> Issue Type: Bug
> Components: General
> Affects Versions: 2.0.4
> Environment: jdk 1.6
> mvn 2.0.4
> windows 2000
> Reporter: Peter Lynch
>
> 1. Create parent pom with a profile activated on the jdk you are running
> maven with
> Inside the profile define a dependencyManagement/dependency to a jar
> explicitly stating a version. Assume in this example it is version 1.0
> 2. Create a child pom defining parent in step 1 as parent. In this child,
> define an explicit dependencies/dependency with the same artifactId and
> groupId as that profile/dependencyManagement/dependency defined in parent
> pom. Only difference being that in the child, the dependency version is set
> to 2.0.
> 3. Run mvn site and look at teh dependency report. The dependency report
> indicates the version of the dependency to be 1.0 ( the one defined in the
> parent pom profile.
> Expected behavior is that the explicit dependency defined in child should
> take precedence.
--
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
