[
https://jira.codehaus.org/browse/MNG-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-3800:
-------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
> dependencyManagement ignores version constraints
> ------------------------------------------------
>
> Key: MNG-3800
> URL: https://jira.codehaus.org/browse/MNG-3800
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.9
> Reporter: Kees van Dieren
>
> Tested the following situation:
> ProjectA (version 0.5.0)
> ProjectB version 0.4.0 has dependency on projectA, with range [0.5.0,)
> ProjectC has a dependencyManagement section, in which projectA is defined on
> version 0.4.0 and projectB is defined on version 0.4.0
> Maven should warn us that this will not work: projectB requires version 0.5.0
> or higher, however this doesn't say anything about this, and just works.
> We have tried the following versions in dependencyManagement:
> <version>[0.4.0]</version>
> <version>0.4.0</version>
> From ranges perspective, I would expect that [0.4.0] should be the correct
> one. However, than the dependencyManagent version gets ignored!
> Version 0.4.0 makes the dependencyManagement apply, but the build does not
> fail on range constraints.
> According to MNG-3396 it should have been solved in 2.0.9, quote from issue:
> " If you try to force a version out of the range in the dependencyManagement
> it is ignored."
> However, we are using that and we still have this problem.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
