[LOG4J2-3601] log4j-slf4j2: change of dependency scope for log4j-core

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.19.0
• Fix Version/s: 2.20.0
• Component/s: SLF4J Bridge
• Assignee: Unassigned
• Reporter: Andy Seaborne
• Created: 18/Sep/22 08:50
• Updated: 06/Feb/23 07:39
• Resolved: 06/Feb/23 05:22

Description

The artifact log4j-slf4j-impl has a scope=runtime dependency on log4j-core. log4j-slf4j18-impl similarly had scope=runtime.

The artifact log4j-slf4j2-impl has a scope=test dependency on log4j-core.

This changed as part of commit 8f63620875 although it seems to be unrelated.

It makes switching over more of a bump. Previously just depending on log4j-slf4j-impl was enough.

Please switch back to a scope=runtime dependency for log4j-slf4j2-impl.

Example: we (Apache Jena) use slf4j in the main code base, and select log4j when it needed for binaries tests so we have multiple places where the dependency happens. We can change - but this may be a user experience for others as well.

[INFO] +- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.18.0:compile
[INFO] |  +- org.apache.logging.log4j:log4j-api:jar:2.18.0:compile
[INFO] |  \- org.apache.logging.log4j:log4j-core:jar:2.18.0:runtime

[INFO] +- org.apache.logging.log4j:log4j-slf4j2-impl:jar:2.19.0:compile
[INFO] |  \- org.apache.logging.log4j:log4j-api:jar:2.19.0:compile

 

Issue Links

• relates to: LOG4J2-3605 log4j-to-slf4j: add runtime logback-classic dependency
• links to: GitHub Pull Request #1064