[jira] Resolved: (DBCP-68) [dbcp] Commons Collection dependency version clash when using Commons DBCP via Maven2

["Phil Steitz (JIRA)" <ji...@apache.org>]

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

Phil Steitz resolved DBCP-68.
-----------------------------

    Resolution: Fixed

1.2.2 has (at last) been released.

> [dbcp] Commons Collection dependency version clash when using Commons DBCP via Maven2
> -------------------------------------------------------------------------------------
>
>                 Key: DBCP-68
>                 URL: https://issues.apache.org/jira/browse/DBCP-68
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: Operating System: All
> Platform: All
>            Reporter: Christoph Cenowa
>             Fix For: 1.2.2
>
>
> When using Maven2 to incorporate Commons DBCP 1.2.1 into your project a
> transient dependency on Commons Collections 2.1 is added. This will clash with
> other Commons Components like Commons Configuration 1.2 for example that depend
> on Commons Collections 3.1. Upon adding Commons DBCP 1.2.1 to your project the
> existing transient dependency on Commons Collections 3.1 gets changed into
> Commons Collections 2.1. This will result in runtime errors like the following:
> java.lang.NoClassDefFoundError: org/apache/commons/collections/map/LinkedMap
> 	at
> org.apache.commons.configuration.BaseConfiguration.<init>(BaseConfiguration.java:53)
> Since Commons Collections is incorporated into most Commons Components please
> update the dependency within Commons DBCP to Commons Collections 3.1 if possible.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org