[jira] [Commented] (CONFIGURATION-451) commons-beanutils in two different version in dependency tree
[
https://issues.apache.org/jira/browse/CONFIGURATION-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050955#comment-13050955
]
Daniel Bimschas commented on CONFIGURATION-451:
---
Sure, if it's fixed, it's fixed. :)
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
[jira] [Commented] (CONFIGURATION-451) commons-beanutils in two different version in dependency tree
[
https://issues.apache.org/jira/browse/CONFIGURATION-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050233#comment-13050233
]
Oliver Heger commented on CONFIGURATION-451:
So what do you suggest to solve the problem?
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
[jira] [Commented] (CONFIGURATION-451) commons-beanutils in two different version in dependency tree
[
https://issues.apache.org/jira/browse/CONFIGURATION-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050257#comment-13050257
]
Joerg Schaible commented on CONFIGURATION-451:
--
Use always commons-beanutils. However, that's already the case in HEAD, so it
is fixed for 1.7.
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
[jira] [Commented] (CONFIGURATION-451) commons-beanutils in two different version in dependency tree
[
https://issues.apache.org/jira/browse/CONFIGURATION-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050505#comment-13050505
]
Oliver Heger commented on CONFIGURATION-451:
Such problems I love the most :-)
So if I understand well, I can directly close this issue. Daniel, is this fine
with you, too?
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
[jira] [Commented] (CONFIGURATION-451) commons-beanutils in two different version in dependency tree
[
https://issues.apache.org/jira/browse/CONFIGURATION-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049979#comment-13049979
]
Oliver Heger commented on CONFIGURATION-451:
Not sure whether I understand your point. There is no need to have both
versions of commons-beanutils in the classpath. The transitive dependency to
version 1.7.0 is overridden by the one specified in the pom. So the maven
classpath ends up with only version 1.8 included. Just do a {{mvn
dependency:copy-dependencies}}. This command puts all dependencies currently
used in a directory. There is only the newest version of beanutils contained.
In your project you also should have *only* version 1.8 of beanutils in the
classpath. Commons Configuration is compatible with it. You can use all new
features of this version in your project.
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
[jira] [Commented] (CONFIGURATION-451) commons-beanutils in two different version in dependency tree
[
https://issues.apache.org/jira/browse/CONFIGURATION-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050035#comment-13050035
]
Joerg Schaible commented on CONFIGURATION-451:
--
You overlooked that two different artifacts are in use: commons-beanutils and
commons-beanutils-core. And if commons-beanutils-core is first in classpath the
rest of the classes are loaded from commons-beanutils. I can imagine that at
some point problems may arise.
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
[jira] [Commented] (CONFIGURATION-451) commons-beanutils in two different version in dependency tree
[
https://issues.apache.org/jira/browse/CONFIGURATION-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] [Commented] (CONFIGURATION-451) commons-beanutils in two different version in dependency tree
[
https://issues.apache.org/jira/browse/CONFIGURATION-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
