[
https://issues.apache.org/jira/browse/ARTEMIS-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437124#comment-17437124
]
Justin Bertram commented on ARTEMIS-3549:
-----------------------------------------
FWIW, {{org.apache.activemq:activemq-artemis-native}} is actually not a module
of the ActiveMQ Artemis project itself. It's split out into its own repo -
[https://github.com/apache/activemq-artemis-native.]
My first thought here is to resolve this by simply removing the logging
dependency from {{activemq-artemis-native}} altogether otherwise this will be
an ongoing problem every time we move to a later versions of logging or maybe
we should have a "parent" project that all projects/modules can use (kind of
like the Apache parent).
What do you think [~clebertsuconic]?
> Mixed versioning of logger utitlies
> -----------------------------------
>
> Key: ARTEMIS-3549
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3549
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: ActiveMQ-Artemis-Native
> Affects Versions: 2.19.0
> Reporter: Greg Turnquist
> Assignee: Clebert Suconic
> Priority: Minor
>
> 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:
> {code:java}
> <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>
> {code}
> This resulted in two different versions of JBoss Logger getting pulled in via
> various transitive dependencies:
> {code}
> +-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
> {code}
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
