[jira] [Updated] (MENFORCER-310) requireUpperBoundDeps resolves wrong version when relocate and dependencyManagement is combined

[ https://issues.apache.org/jira/browse/MENFORCER-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kees van Dieren updated MENFORCER-310: -- Description: We have a dependency foo:bar:1.0 which has been relocated to com:foo:ba

[jira] [Updated] (MENFORCER-310) requireUpperBoundDeps resolves wrong version when relocate and dependencyManagement is combined

[ https://issues.apache.org/jira/browse/MENFORCER-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kees van Dieren updated MENFORCER-310: -- Summary: requireUpperBoundDeps resolves wrong version when relocate and dependencyMa

[jira] [Created] (MENFORCER-310) requireUpperbounds resolves wrong version when relocate and dependencyManagement is combined

Kees van Dieren created MENFORCER-310: - Summary: requireUpperbounds resolves wrong version when relocate and dependencyManagement is combined Key: MENFORCER-310 URL: https://issues.apache.org/jira/browse/MENFO

[jira] Created: (MNG-3800) dependencyManagement ignores version constraints

dependencyManagement ignores version constraints Key: MNG-3800 URL: http://jira.codehaus.org/browse/MNG-3800 Project: Maven 2 Issue Type: Bug Components: Dependencies Affects Ver

[jira] Commented: (MNG-2525) SNAPSHOT dependencies aren't found when repository has 'release' disabled and a version range is used

[ http://jira.codehaus.org/browse/MNG-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151464#action_151464 ] Kees van Dieren commented on MNG-2525: -- Ranges should not lead to snapshot dependencies, unless a