tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Romain Manni-Bucau (JIRA)" <>
Subject [jira] [Commented] (OPENEJB-2036) openejb-core has conflicting dependencies to commons-pool
Date Tue, 20 Aug 2013 13:40:52 GMT


Romain Manni-Bucau commented on OPENEJB-2036:


IMO it is a bug in the maven rule.

Maven dependency rules respect the level of the hierarchy. That's the reason why we forced
the version in openejb-core pom of commons-pool to override commons-dbcp dependency and all
other transitive deps of the project (that's why exclusion is not a solution, because we would
do it everywhere which is a pain to maintain when upgrading versions).

> openejb-core has conflicting dependencies to commons-pool
> ---------------------------------------------------------
>                 Key: OPENEJB-2036
>                 URL:
>             Project: OpenEJB
>          Issue Type: Bug
>    Affects Versions: 4.5.1
>            Reporter: Jens Bannmann
>            Priority: Minor
> I activated the Maven Enforcer dependency convergence rule (see [])
for my project, and got an error caused by openejb:
>     [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce) @ myartifact ---
>     [WARNING] 
>     Dependency convergence error for commons-pool:commons-pool:1.5.4 paths to dependency
>     +-mygroup:myartifact:1.0-SNAPSHOT
>       +-org.apache.openejb:openejb-core:4.5.1
>         +-commons-dbcp:commons-dbcp:1.4
>           +-commons-pool:commons-pool:1.5.4
>     and
>     +-mygroup:myartifact:1.0-SNAPSHOT
>       +-org.apache.openejb:openejb-core:4.5.1
>         +-commons-pool:commons-pool:1.5.7
> In my opinion, openejb-core has to either
> a) use a version of commons-dbcp that uses the same version of commons-pool (1.5.7),
> b) exclude the transitive dependency to 1.5.4.
> Besides ensuring correctness within OpenEJB, this has the added benefit of not breaking
downstream builds which use this rule from Maven Enforcer Plugin.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message