You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Kees van Dieren (JIRA)" <ji...@apache.org> on 2018/07/16 09:32:00 UTC

[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/MENFORCER-310
             Project: Maven Enforcer Plugin
          Issue Type: Bug
          Components: Standard Rules
            Reporter: Kees van Dieren


We have a dependency foo:bar:1.0 which has been relocated to com:foo:bar:1.1

In dependencyManagement we have defined com:foo:bar:1.2

Maven dependency tree shows 1.2 version

However, requireUpperbounds will fail with exception that 1.1 is resolved.

Maybe [~ge0ffrey.desmet] can have a look at it :)?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)