harshab054 commented on issue #14019: URL: https://github.com/apache/maven/issues/14019#issuecomment-6954685584
I investigated the dependency leak in Maven 3.10.1 and confirmed that "maven-resolver-provider" exposes "jcl-over-slf4j" as a non-optional runtime dependency. Resolver 2.0.25 already marks this dependency optional, with the expectation that the application provides a JCL implementation. Making it optional in Maven's provider POM removes it from downstream consumers' dependency trees while preserving it on the provider's own test classpath. I also verified that Apache HttpClient 4.5.14 requires the JCL API, and that "commons-logging:1.3.4" can provide that API while delegating logging to SLF4J. There seem to be two possible scopes: 1. Make "jcl-over-slf4j" optional in the Maven 3.10.x provider, preventing it from leaking to downstream consumers. 2. Replace the bridge with standard Commons Logging throughout Maven, including the CLI distribution. Which direction would you prefer? I would like to align the fix with the intended scope before submitting a revised PR. -- 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]
