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 15:18:51 GMT


Romain Manni-Bucau commented on OPENEJB-2036:

we checked it was working before and updated because we had issues with previous versions.
Since dbcp doesn't have issues in its code it didn't re-released for updating pool. Our pom
is correct and i don't want to change our pom for a wrong rule of a maven plugin.
> 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