You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "Vlad Rozov (JIRA)" <ji...@apache.org> on 2018/02/20 22:51:00 UTC
[jira] [Commented] (APEXCORE-805) There are dependency conflicts in
apex-core/engine module
[ https://issues.apache.org/jira/browse/APEXCORE-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370703#comment-16370703 ]
Vlad Rozov commented on APEXCORE-805:
-------------------------------------
[~PandaMonkey] exclude {{test}} scope from your analysis and see if there are any conflicts present.
> 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
>
>
> 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)