[ 
https://issues.apache.org/jira/browse/MENFORCER-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MENFORCER-280.
------------------------------------
      Assignee: Robert Scholte
    Resolution: Done

This has been fixed as part of MENFORCER-277
I've added an IT with 
[faaf5c118bd9cda06cecca94ab3f9656c1cb7927|https://gitbox.apache.org/repos/asf?p=maven-enforcer.git;a=commit;h=faaf5c118bd9cda06cecca94ab3f9656c1cb7927]
 which confirms that the dependency graph implementation of Maven3 has been 
improved and fixes the Maven2 resolution bug.

> Enforcer dependency convergence stumbles on selenium-java
> ---------------------------------------------------------
>
>                 Key: MENFORCER-280
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-280
>             Project: Maven Enforcer Plugin
>          Issue Type: Bug
>    Affects Versions: 3.0.0-M1
>            Reporter: Axel Fontaine
>            Assignee: Robert Scholte
>            Priority: Major
>
> When running the dependency convergence check, we get this impossible result:
> {noformat}
> Dependency convergence error for org.seleniumhq.selenium:selenium-java:3.3.1 
> paths to dependency are:
> +-com.mywebapp:0-SNAPSHOT
>   +-org.seleniumhq.selenium:selenium-java:3.3.1
> and
> +-com.mywebapp:0-SNAPSHOT
>   +-org.seleniumhq.selenium:selenium-java:3.3.1
>     +-org.seleniumhq.selenium:selenium-java:3.1.0
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to