-
Bug
-
Resolution: Won't Do
-
Minor
-
None
-
None
-
None
-
None
-
False
-
None
-
False
-
-
-
-
-
-
-
In the root pom we have:
<maven.min.version>3.6.0</maven.min.version>
But trying to build with any maven less than 3.6.3 fails:
[INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (ban-bad-dependencies) @ wildfly-mp-feature-pack-galleon-common --- [WARNING] Dependency convergence error for jakarta.annotation:jakarta.annotation-api:1.3.5.redhat-00003 paths to dependency are: +-org.jboss.eap:wildfly-mp-feature-pack-galleon-common:4.0.1.GA-redhat-SNAPSHOT +-io.smallrye:smallrye-fault-tolerance:5.2.1.redhat-00009 +-jakarta.annotation:jakarta.annotation-api:1.3.5.redhat-00003 and +-org.jboss.eap:wildfly-mp-feature-pack-galleon-common:4.0.1.GA-redhat-SNAPSHOT +-io.smallrye.reactive:smallrye-reactive-messaging-provider:3.13.0.redhat-00001 +-jakarta.annotation:jakarta.annotation-api:1.3.5 [WARNING] Rule 1: org.apache.maven.plugins.enforcer.DependencyConvergence failed with message: Failed while enforcing releasability. See above detailed error message.
Both smallrye-fault-tolerance and smallrye-reactive-messaging-provider exclude all transitives, so I regard this as a maven bug, likely the same one discussed in the root pom for vertx-core:
<dependency>
<groupId>io.vertx</groupId>
<artifactId>vertx-core</artifactId>
<version>${version.io.vertx.vertx}</version>
<exclusions>
<!--
For some reason a wildcard exclusion here triggers a dependency convergence
error in the enforcer plugin. List them all individually.
TODO replace with a wildcard exclusion once the world is on maven 3.6.2+
-->
<exclusion>
<groupId>io.netty</groupId>
...
We could spend a lot of time trying to do something like what is done with vertx-core, or we could just decide that the current minimum is incorrect and change it to 3.6.3.
- is related to
-
JBEAP-25868 Dependency management should exclude all io.netty dependencies from vertx-core
-
- Verified
-
