You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "PandaMonkey (JIRA)" <ji...@apache.org> on 2018/02/10 06:13:00 UTC

[jira] [Created] (ACCUMULO-4812) Dependency Conflict: different Jars contain the incompatible classes with the same name, which leads to NoSuchMethodException

PandaMonkey created ACCUMULO-4812:
-------------------------------------

             Summary: 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
             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 be throw the "*NoSuchMethodException*" or "*NoSuchMethodError*" if the duplicate classes are inconsistent!! So we spend some energy to scan the different features of these duplicate classes, the details are shown in the attachment [^Conflicting details.txt]. Please pay attention to it! Hope our report can help you. Thanks ^_^.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)