maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roy van Rijn (Jira)" <>
Subject [jira] [Commented] (MENFORCER-280) Enforcer dependency convergence stumbles on selenium-java
Date Wed, 29 Jul 2020 13:46:00 GMT


Roy van Rijn commented on MENFORCER-280:

Two things:

First: I'm able to reproduce this and can't yet explain where the *3.1.0* comes from. To reproduce
use the following pom:


              <dependencyConvergence />

This results in the error above which is odd... because the pom file points to 3.3.1, not

As a quick fix I tried upgrading the dependency-tree version to something higher than 2.2,
going to DependencyGraphBuilder, but this doesn't work because of issue [MSHARED-788].

I'll try to digg deeper and find why the dependency-tree finds a 3.1.0 version of selenium-java.

> Enforcer dependency convergence stumbles on selenium-java
> ---------------------------------------------------------
>                 Key: MENFORCER-280
>                 URL:
>             Project: Maven Enforcer Plugin
>          Issue Type: Bug
>    Affects Versions: 3.0.0-M1
>            Reporter: Axel Fontaine
>            Priority: Major
> When running the dependency convergence check, we get this impossible result:
> {{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}}

This message was sent by Atlassian Jira

View raw message