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

Jens Bannmann updated OPENEJB-2036:
-----------------------------------

    Description: 
I activated the Maven Enforcer dependency convergence rule (see 
http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html) 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 are:
    +-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), or
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.

  was:
I activated the Maven Enforcer dependency convergence rule (see 
<http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html>) 
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 are:
    +-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), or
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.

    
> openejb-core has conflicting dependencies to commons-pool
> ---------------------------------------------------------
>
>                 Key: OPENEJB-2036
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-2036
>             Project: OpenEJB
>          Issue Type: Bug
>    Affects Versions: 4.5.1
>            Reporter: Jens Bannmann
>            Priority: Minor
>
> I activated the Maven Enforcer dependency convergence rule (see 
> http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html) 
> 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 are:
>     +-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), or
> 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: http://www.atlassian.com/software/jira

Reply via email to