[
https://issues.apache.org/jira/browse/CONFIGURATION-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13047376#comment-13047376
]
Oliver Heger commented on CONFIGURATION-451:
--------------------------------------------
This should not be an issue in this case because commons-beanutils 1.8 is
binary compatible to version 1.7. Also as pointed out on the dependencies page
(http://commons.apache.org/configuration/dependencies.html) Commons
Configuration has been tested with both versions.
Some of the Maven experts may correct me if I am wrong, but I think a situation
where a dependency is declared directly and also is referenced transitively (in
a different version) is not that uncommon. Maven can handle this and ensures
that in its classpath only a single version of the library (the newest one) is
contained.
However, if the different versions of the library are incompatible and the
authors did not provide any means for dealing with this (e.g. by changing the
package structure), then you are in trouble.
> commons-beanutils in two different version in dependency tree
> -------------------------------------------------------------
>
> Key: CONFIGURATION-451
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-451
> Project: Commons Configuration
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.6
> Reporter: Daniel Bimschas
> Priority: Minor
> Labels: build, maven
>
> The Maven dependency tree (mvn dependency:tree) delivers:
> {quote}
> [INFO] | \- commons-configuration:commons-configuration:jar:1.6:compile
> [INFO] | +- commons-collections:commons-collections:jar:3.2.1:compile
> [INFO] | +- commons-logging:commons-logging:jar:1.1.1:compile
> [INFO] | +- commons-digester:commons-digester:jar:1.8:compile
> [INFO] | | \- commons-beanutils:commons-beanutils:jar:1.7.0:compile
> [INFO] | \- commons-beanutils:commons-beanutils-core:jar:1.8.0:compile
> {quote}
> There is two times the commons-beanutils package with two different versions
> which can potentially cause problems during runtime as it is not clear which
> version is first in the classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
