[ARTEMIS-3549] Mixed versioning of logger utitlies

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Invalid
• Affects Version/s: 2.19.0
• Component/s: ActiveMQ-Artemis-Native
• Assignee: Clebert Suconic
• Reporter: Greg Turnquist
• Created: 01/Nov/21 18:05
• Updated: 10/May/23 19:04
• Resolved: 10/May/23 19:02

Description

While building Spring Web Services against Artemis Jakarta JMS 2.19.0, I ran into a conflict of JBoss Logger versions between various components of Artemis.

Clause added to my pom.xml:

<dependency>
    <groupId>org.apache.activemq</groupId>
    <artifactId>artemis-jakarta-server</artifactId>
    <version>2.19.0</version>
    <scope>test</scope>
    <exclusions>
        <exclusion> <!-- Use version provided by Jakarta EE 9 POM -->
            <groupId>jakarta.jms</groupId>
            <artifactId>jakarta.jms-api</artifactId>
        </exclusion>
    </exclusions>
</dependency>

This resulted in two different versions of JBoss Logger getting pulled in via various transitive dependencies:

+-org.springframework.ws:spring-ws-support:4.0.0-SNAPSHOT
  +-org.apache.activemq:artemis-jakarta-server:2.19.0
    +-org.apache.activemq:artemis-server:2.19.0
      +-org.apache.activemq:artemis-jdbc-store:2.19.0
        +-org.jboss.logging:jboss-logging:3.4.2.Final
and
+-org.springframework.ws:spring-ws-support:4.0.0-SNAPSHOT
  +-org.apache.activemq:artemis-jakarta-server:2.19.0
    +-org.apache.activemq:artemis-server:2.19.0
      +-org.apache.activemq:activemq-artemis-native:1.0.2
        +-org.jboss.logging:jboss-logging:3.3.1.Final

Since I only have a single dependency, there is no way to exclude something in a given transitive, thus my only choice is to disable maven-enforcer-plugin's dependency convergence check.

If the ActiveMQ Artemis Native module could be aligned to work with the same version of JBoss Logging as all the other modules, that would make it possible to avoid this mismatch of versions.

NOTE: If you happen to use Maven, applying maven-enforcer-plugin to your own base may simplify spotting such errors.

Issue Links

• is related to: ARTEMIS-4020 switch to using SLF4J for logging API and use Log4j 2 for broker distribution