[
http://jira.codehaus.org/browse/MNG-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98540
]
Brett Porter commented on MNG-3033:
-----------------------------------
if you are referring to including the latter dependency as is, rather than in
dependencyManagement, then that behaviour is by design (depMgmt is inherited).
If it is in depMgmt, then it's a bug and this can be reopened.
> DependencyManagement override version if declared in child
> ----------------------------------------------------------
>
> Key: MNG-3033
> URL: http://jira.codehaus.org/browse/MNG-3033
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.5, 2.0.6
> Reporter: hugo lassiege
>
> Hi,
> I'm currently in maven 2.0.5 but I tried in 2.0.6
> If I declare a dependency in a father pom within a dependencyManagement like
> this :
> <dependency>
> <groupId>A</groupId>
> <artifactId>A</artifactId>
> <version>1.0</version>
> </dependency>
> and if I want to override the version in the child :
> <dependency>
> <groupId>A</groupId>
> <artifactId>A</artifactId>
> <version>1.1</version>
> </dependency>
> I get the version 1.0. It seems it was already reported in this issue :
> http://jira.codehaus.org/browse/MNG-1577 but was not the main purpose and was
> not fixed.
> Regards.
--
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
