[ 
http://issues.apache.org/jira/browse/DBCP-68?page=comments#action_12435302 ] 
            
Stephen Colebourne commented on DBCP-68:
----------------------------------------

Upgrading to a later version of collections shouldn't prove to be a problem. 
But, I agree with the proposed solution of removng the dependency in this case. 
Just ensure that neither class being copied is in the public API at the moment, 
or in the future.

> [dbcp] Commons Collection dependency version clash when using Commons DBCP 
> via Maven2
> -------------------------------------------------------------------------------------
>
>                 Key: DBCP-68
>                 URL: http://issues.apache.org/jira/browse/DBCP-68
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.2 Final
>         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.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to