[LOG4J2-3370] Add Support for SLF4J 2.0

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.17.1
• Fix Version/s: 2.19.0
• Component/s: SLF4J Bridge
• Flags: Important

Language

English

• Assignee: Piotr Karwasz
• Reporter: Timon H.
• Created: 27/Jan/22 12:56
• Updated: 16/Sep/22 15:37
• Resolved: 04/Sep/22 05:39

Description

The SLF4J Bridge (log4j-slf4j18-impl:2.17.1) is currently broken as it contains the same typo bug of SLF4J-API which was fixed in SLF4J-API 2.0.0-alpha3 and therefore leads to an API mismatch error. In the org.apache.logging.slf4j.SLF4JServiceProvider, the getRequesteApiVersion-Method need to be refactored to getRequestedApiVersion.

See the Changelog of SLF4J-API 2.0.0-alpha3: 

• The getRequesteApiVersion method in SLF4JServiceProvider was renamed as getRequestedApiVersion. This fixes SLF4J-516.

This leads to the following exception during the use of log4j-slf4j18-impl:2.17.1 with the current SLF4J-API:

Unexpected problem occured during version sanity check
Reported exception:
java.lang.AbstractMethodError: Receiver class org.apache.logging.slf4j.SLF4JServiceProvider does not define or inherit an implementation of the resolved method 'abstract java.lang.String getRequestedApiVersion()' of interface org.slf4j.spi.SLF4JServiceProvider.
    at org.slf4j.LoggerFactory.versionSanityCheck(LoggerFactory.java:297)

Issue Links

• is related to: LOG4J2-3139 Startup errors with SLF4J 2.0.0-alpha4
• links to: GitHub Pull Request #1023