You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
jcl-over-slf4j is considered deprecated, replace directly with commons-logging 1.3.0+ #2174
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 apache/commons-logging#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.
Activity
pzygielo commentedon Oct 4, 2026
Also
org.apache.maven.reporting:maven-reporting-impl:3.2.0bringscommons-logging:commons-logging:jar:1.4.0org.apache.maven:maven-core:3.10.0brings (frommaven-resolver-transport-apacheI guess)org.slf4j:jcl-over-slf4j:2.0.20This causes duplicate classes (and enforcer finding
in build of some reporting plugin).
cstamas commentedon Oct 12, 2026
jcl is not yet deprecated qos-ch/slf4j#403
Agreed with assessment. @pzygielo pls report this to maven reporting too
slawekjaranowski commentedon Oct 12, 2026
in reporting-imp we have:
and
slawekjaranowski commentedon Oct 12, 2026
In Maven core also we have jcl-over-slf4