[ https://issues.apache.org/jira/browse/APEXCORE-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373018#comment-16373018 ]
Vlad Rozov commented on APEXCORE-805: ------------------------------------- [~PandaMonkey] Conflict with {{org.eclipse.jetty:jetty-servlet}} caused unit test failure so is the explicit handling in pom.xml. As existing conflicts do not affect unit test, I don't see a need to change anything urgently until either hadoop version change or update to other libraries that will cause unit tests to fail. > There are dependency conflicts in apex-core/engine module > --------------------------------------------------------- > > Key: APEXCORE-805 > URL: https://issues.apache.org/jira/browse/APEXCORE-805 > Project: Apache Apex Core > Issue Type: Bug > Affects Versions: 3.6.0 > Reporter: PandaMonkey > Priority: Minor > Attachments: apex-core-conflicts.txt, compare.txt > > > Hi, we found four pairs of JAR files in apex-core/engine contain duplicate > classes. > 1. > jar-pair:<*org.eclipse.jetty.orbit:javax.servlet*:3.0.0.v201112011016:><*javax.servlet:servlet-api*:2.5:> > 2. > jar-pair:<javax.servlet:*javax.servlet-api*:3.0.1:><javax.servlet:*servlet-api*:2.5:> > 3. > jar-pair:<javax.servlet:*servlet-api:*2.5:><org.glassfish:*javax.servlet*:3.1:> > 4. > jar-pair:<*com.google.inject:guice:4.0:no_aop*><*com.google.inject:guice:3.0*:> > Furthermore, by static analysis, we found these duplicate classes have > different implementations. As the JVM only load the classes present first on > the classpath and shadow the other duplicate ones with the same name. So the > problem will lead to the *"NoSuchMethodException"* or *"NoSuchMethodError"*. > The conflicting details are listed in the attachment. Hope this can help you. > Thanks![^apex-core-conflicts.txt] -- This message was sent by Atlassian JIRA (v7.6.3#76005)