[
https://issues.apache.org/jira/browse/CONFIGURATION-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049057#comment-13049057
]
Daniel Bimschas commented on CONFIGURATION-451:
-----------------------------------------------
Actually, I don't know of any issue that is caused except of some warnings of a
library I'm using that does custom classloading and gives warnings about this.
It my be true that Commons Configuration works with both versions. However, if
there's an application that uses Commons Beanutils and Commons Configuration I
could imagine problems can happen if the application itself relies on e.g., 1.8
features and has 1.7 in the classpath.
> 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
