[
https://issues.apache.org/jira/browse/ACCUMULO-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364829#comment-16364829
]
Christopher Tubbs commented on ACCUMULO-4812:
---------------------------------------------
Thanks for the notice! At the very least, we should caution our users to be
careful about how they construct their class path for production.
> Dependency Conflict: different Jars contain the incompatible classes with the
> same name, which leads to NoSuchMethodException
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: ACCUMULO-4812
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4812
> Project: Accumulo
> Issue Type: Bug
> Components: core
> Affects Versions: 2.0.0
> Reporter: PandaMonkey
> Priority: Major
> Labels: releasenotes
> Fix For: 2.0.0
>
> Attachments: Conflicting details.txt
>
>
> Hi, by analyzing the accumulo-core:2.0.0-SNAPSHOT
> accumulo-master\core\pom.xml file, we found that several duplicate classes
> exist in different JARs: "commons-beanutils:commons-*beanutils-core*:1.8.0"
> and "commons-beanutils:commons-*beanutils*:1.7.0". As the JVM only load the
> classes present first on the classpath and shadow the other duplicate ones
> with the same name. It would throw the "*NoSuchMethodException*" or
> "*NoSuchMethodError*" if the duplicate classes are inconsistent! So we spend
> some energy to scan the different features between these duplicate classes.
> The conflicting details are listed in the attachment. Please pay attention to
> it. Hope our report can help you. Thanks :).
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
