[ 
https://issues.apache.org/jira/browse/MENFORCER-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16640781#comment-16640781
 ] 

Karl Heinz Marbaise commented on MENFORCER-310:
-----------------------------------------------

Can you create a working example otherwise we have no chance to reproduce the 
issue....

> requireUpperBoundDeps 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
>            Priority: Major
>
> 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, requireUpperBoundDeps 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)

Reply via email to