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

PandaMonkey updated ARTEMIS-1674:
---------------------------------
    Description: 
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 as 
follows:

" org.jboss.logging.LogMessage 
 org.jboss.logging.Log4j2LoggerProvider 
 org.jboss.logging.MessageLogger 
 org.jboss.logging.DelegatingBasicLogger 
 org.jboss.logging.Slf4jLocationAwareLogger$1 
 org.jboss.logging.Logger 
 org.jboss.logging.Log4jLoggerProvider 
 org.jboss.logging.MDC 
 org.jboss.logging.JBossLogManagerProvider 
 org.jboss.logging.NDC 
 org.jboss.logging.LoggingClass 
 org.jboss.logging.LoggerProvider 
 org.jboss.logging.AbstractLoggerProvider$Entry 
org.jboss.logging.Slf4jLoggerProvider 
 org.jboss.logging.Message$Format 
 org.jboss.logging.JBossLogRecord
 org.jboss.logging.Messages 
 org.jboss.logging.Logger$1
 org.jboss.logging.LoggerProviders$1 
 org.jboss.logging.SerializedLogger 
 org.jboss.logging.Param 
 org.jboss.logging.Messages$1 
 org.jboss.logging.Log4jLogger 
 org.jboss.logging.JBossLogManagerProvider$1 
 org.jboss.logging.Log4j2Logger
 org.jboss.logging.LoggerProviders
 org.jboss.logging.BasicLogger
 org.jboss.logging.MessageBundle 
 org.jboss.logging.FormatWith 
 org.jboss.logging.Field 
 org.jboss.logging.Message 
 org.jboss.logging.Logger$Level 
 org.jboss.logging.ParameterConverter 
 org.jboss.logging.AbstractLoggerProvider 
 org.jboss.logging.Slf4jLogger 
 org.jboss.logging.JDKLogger 
 org.jboss.logging.Slf4jLocationAwareLogger e
 org.jboss.logging.Cause 
 org.jboss.logging.AbstractMdcLoggerProvider
 org.jboss.logging.JDKLevel
 org.jboss.logging.Property 
 org.jboss.logging.JBossLogManagerLogger 
 org.jboss.logging.JDKLoggerProvider"

Of them, two versions of classes "org.jboss.logging.Log4j2LoggerProvider", 
"org.jboss.logging.MDC", "org.jboss.logging.JBossLogManagerProvider", 
"org.jboss.logging.Slf4jLoggerProvider", "org.jboss.logging.Log4j2Logger", 
"org.jboss.logging.JBossLogManagerLogger", "org.jboss.logging.JDKLogger" in 
these two libraries, have different features. The conflicting feature's details 
are shown in the attachment. Please notice this problem, it brings high risks 
of classpath issues during the evolution.

  was:
Hi, by analyzing artemis-cdi-client:2.5.0-SNAPSHOT "artemis-cdi-client\pom.xml" 
and the 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 as 
follows:

" org.jboss.logging.LogMessage 
org.jboss.logging.Log4j2LoggerProvider 
org.jboss.logging.MessageLogger 
org.jboss.logging.DelegatingBasicLogger 
org.jboss.logging.Slf4jLocationAwareLogger$1 
org.jboss.logging.Logger 
org.jboss.logging.Log4jLoggerProvider 
org.jboss.logging.MDC 
org.jboss.logging.JBossLogManagerProvider 
org.jboss.logging.NDC 
org.jboss.logging.LoggingClass 
org.jboss.logging.LoggerProvider 
org.jboss.logging.AbstractLoggerProvider$Entry 
org.jboss.logging.Slf4jLoggerProvider 
org.jboss.logging.Message$Format 
org.jboss.logging.JBossLogRecord
org.jboss.logging.Messages 
org.jboss.logging.Logger$1
org.jboss.logging.LoggerProviders$1 
org.jboss.logging.SerializedLogger 
org.jboss.logging.Param 
org.jboss.logging.Messages$1 
org.jboss.logging.Log4jLogger 
org.jboss.logging.JBossLogManagerProvider$1 
org.jboss.logging.Log4j2Logger
org.jboss.logging.LoggerProviders
org.jboss.logging.BasicLogger
org.jboss.logging.MessageBundle 
org.jboss.logging.FormatWith 
org.jboss.logging.Field 
org.jboss.logging.Message 
org.jboss.logging.Logger$Level 
org.jboss.logging.ParameterConverter 
org.jboss.logging.AbstractLoggerProvider 
org.jboss.logging.Slf4jLogger 
org.jboss.logging.JDKLogger 
org.jboss.logging.Slf4jLocationAwareLogger e
org.jboss.logging.Cause 
org.jboss.logging.AbstractMdcLoggerProvider
org.jboss.logging.JDKLevel
org.jboss.logging.Property 
org.jboss.logging.JBossLogManagerLogger 
org.jboss.logging.JDKLoggerProvider"

Of them, two versions of classes "org.jboss.logging.Log4j2LoggerProvider", 
"org.jboss.logging.MDC", "org.jboss.logging.JBossLogManagerProvider", 
"org.jboss.logging.Slf4jLoggerProvider", "org.jboss.logging.Log4j2Logger", 
"org.jboss.logging.JBossLogManagerLogger", "org.jboss.logging.JDKLogger" in 
these two libraries, have different features. The conflicting feature's details 
are shown in the attachment. Please notice this problem, it brings high risks 
of classpath issues during the evolution.


> Dependency Conflict : Conclicting 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: Major
>              Labels: features
>             Fix For: 2.5.0
>
>         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 as 
> follows:
> " org.jboss.logging.LogMessage 
>  org.jboss.logging.Log4j2LoggerProvider 
>  org.jboss.logging.MessageLogger 
>  org.jboss.logging.DelegatingBasicLogger 
>  org.jboss.logging.Slf4jLocationAwareLogger$1 
>  org.jboss.logging.Logger 
>  org.jboss.logging.Log4jLoggerProvider 
>  org.jboss.logging.MDC 
>  org.jboss.logging.JBossLogManagerProvider 
>  org.jboss.logging.NDC 
>  org.jboss.logging.LoggingClass 
>  org.jboss.logging.LoggerProvider 
>  org.jboss.logging.AbstractLoggerProvider$Entry 
> org.jboss.logging.Slf4jLoggerProvider 
>  org.jboss.logging.Message$Format 
>  org.jboss.logging.JBossLogRecord
>  org.jboss.logging.Messages 
>  org.jboss.logging.Logger$1
>  org.jboss.logging.LoggerProviders$1 
>  org.jboss.logging.SerializedLogger 
>  org.jboss.logging.Param 
>  org.jboss.logging.Messages$1 
>  org.jboss.logging.Log4jLogger 
>  org.jboss.logging.JBossLogManagerProvider$1 
>  org.jboss.logging.Log4j2Logger
>  org.jboss.logging.LoggerProviders
>  org.jboss.logging.BasicLogger
>  org.jboss.logging.MessageBundle 
>  org.jboss.logging.FormatWith 
>  org.jboss.logging.Field 
>  org.jboss.logging.Message 
>  org.jboss.logging.Logger$Level 
>  org.jboss.logging.ParameterConverter 
>  org.jboss.logging.AbstractLoggerProvider 
>  org.jboss.logging.Slf4jLogger 
>  org.jboss.logging.JDKLogger 
>  org.jboss.logging.Slf4jLocationAwareLogger e
>  org.jboss.logging.Cause 
>  org.jboss.logging.AbstractMdcLoggerProvider
>  org.jboss.logging.JDKLevel
>  org.jboss.logging.Property 
>  org.jboss.logging.JBossLogManagerLogger 
>  org.jboss.logging.JDKLoggerProvider"
> Of them, two versions of classes "org.jboss.logging.Log4j2LoggerProvider", 
> "org.jboss.logging.MDC", "org.jboss.logging.JBossLogManagerProvider", 
> "org.jboss.logging.Slf4jLoggerProvider", "org.jboss.logging.Log4j2Logger", 
> "org.jboss.logging.JBossLogManagerLogger", "org.jboss.logging.JDKLogger" in 
> these two libraries, have different features. The conflicting feature's 
> details are shown in the attachment. Please notice this problem, it brings 
> high risks of classpath issues during the evolution.



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

Reply via email to