[
https://issues.apache.org/jira/browse/AMQ-6898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-6898.
-----------------------------
Resolution: Not A Problem
> Dependency conflict problems in different JARs
> <org.apache.geronimo.specs:geronimo-jms_1.1_spec:1.1.1:><org.apache.geronimo.specs:geronimo-jms_2.0_spec:1.0-alpha-2:>,
> which brings high risks of NoSuchMethodException
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-6898
> URL: https://issues.apache.org/jira/browse/AMQ-6898
> Project: ActiveMQ
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 5.15.3
> Reporter: PandaMonkey
> Priority: Major
> Labels: features
> Attachments: activemq-amqp—conflicts.txt
>
>
> Hi, same classes exist in two different JARs:
> <*org.apache.geronimo.specs:geronimo-jms_1.1_spec:*1.1.1:> and
> <*org.apache.geronimo.specs:geronimo-jms_2.0_spec*:1.0-alpha-2:>.
> The same problem also exist in JAR pair
> <*commons-beanutils:commons-beanutils-core*:1.8.0:> and
> <*commons-beanutils:commons-beanutils*:1.9.3:>.
> And after further analyzing the source code, we found that these duplicate
> classes have different implementations, which would leads to the
> *NoSuchMethodException*! If the classes with the same name on the classpath,
> then the only the first present one can be loaded. So it affects the program
> behaviors. The differences between are listed in the attachment. Hope this
> can help you. Thanks!
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
