activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "PandaMonkey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ARTEMIS-1674) Dependency Conflict : Conflicting classes existing in two libraries
Date Thu, 22 Feb 2018 04:44:00 GMT

     [ https://issues.apache.org/jira/browse/ARTEMIS-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

PandaMonkey updated ARTEMIS-1674:
---------------------------------
    Priority: Minor  (was: Major)

> Dependency Conflict : Conflicting classes existing in two libraries
> -------------------------------------------------------------------
>
>                 Key: ARTEMIS-1674
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1674
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.4.0
>         Environment: [^Conflicting libs.TXT]
>            Reporter: PandaMonkey
>            Priority: Minor
>              Labels: features
>         Attachments: Conflicting libs.TXT
>
>
> Hi, by analyzing artemis-cdi-client:2.5.0-SNAPSHOT "artemis-cdi-client\pom.xml" and its
bytecodes, we found libraries "org.jboss.weld.se:weld-se:2.4.0.Final" and "org.jboss.logging:jboss-logging:3.3.1.Final"
contains duplicate classes.
>  The following duplicate class pairs having the same names but their internal implementations
are different in different JARs:
>  "org.jboss.logging.Log4j2LoggerProvider", 
>  "org.jboss.logging.MDC", 
>  "org.jboss.logging.JBossLogManagerProvider",
>  "org.jboss.logging.Slf4jLoggerProvider", 
>  "org.jboss.logging.Log4j2Logger", 
>  "org.jboss.logging.JBossLogManagerLogger", 
> .........
> Some methods only exist in one class version:
>  org.jboss.logging.Log4j2LoggerProvider: void clearMdc()
>  org.jboss.logging.Log4jLoggerProvider: void clearMdc()
>  org.jboss.logging.MDC: void clear()
>  ......
> Please notice this problem. As the JVM only load the classes present first on the classpath
and shadow the other duplicate ones with the same name. So it brings high risks of classpath
issues during the truck evolution process, which may throw the *java.lang.NoSuchMethodException*
at runtime.
> The conflicting features' details are shown in the attachment. Hope this report can help
you, thanks!



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

Mime
View raw message