slachiewicz opened a new pull request, #2231: URL: https://github.com/apache/maven-resolver/pull/2231
Fixes #2174. `maven-resolver-transport-apache` no longer passes `jcl-over-slf4j` on to its consumers. Through `maven-core` (provided) it reached plugin classpaths next to `commons-logging` and tripped `banDuplicateClasses`. The application now picks the JCL implementation: - The Maven distribution already declares `jcl-over-slf4j` in `apache-maven/pom.xml` (3.10.x and master), so `lib/` keeps the same content. - `maven-resolver-supplier-mvn3` and `-mvn4` declare it themselves, so supplier users see no change. - Other code that runs the Apache transport with no JCL on the classpath gets `NoClassDefFoundError: org/apache/commons/logging/LogFactory` and must add `jcl-over-slf4j` or `commons-logging` 1.3+. Maven 4's `maven-testing` and `maven-cli` depend on transport-apache directly, so they may want the same explicit dependency. Verified: a consumer of transport-apache plus `commons-logging:1.3.5`, `mvn dependency:list` → only `commons-logging` provides `org.apache.commons.logging`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
