hazendaz opened a new issue, #2174: URL: https://github.com/apache/maven-resolver/issues/2174
### Affected version 2.0.24 ### Bug description note: Not really a bug but seemed best selection. In my builds I have strict handling against usage of 'jcl-over-slf4j'. After maven 3.10.0 dropped, enforcer plugin rule for me alerted to the resolver 2.x using jcl-over-slf4j (2.0.24 tested here). Per https://github.com/apache/commons-logging/pull/177, jcl variants are entirely obsolete. Therefore, can this be replaced with commons-logging inside the maven-resolver-transport-apache module? Currently there is an exclusion in that pom against commons-logging with jcl-over-slf4j added. The current commons-logging is 1.4.0. As this isn't a true bug, just missed opportunity, I can work around the concern for now but would be nice to see fixed in later revision. -- 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]
