[
https://issues.apache.org/jira/browse/LOG4J2-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605897#comment-17605897
]
Ralph Goers commented on LOG4J2-3370:
-------------------------------------
[~ctubbsii] Please review the dev list before asking questions in Jira.
> Add Support for SLF4J 2.0
> -------------------------
>
> Key: LOG4J2-3370
> URL: https://issues.apache.org/jira/browse/LOG4J2-3370
> Project: Log4j 2
> Issue Type: New Feature
> Components: SLF4J Bridge
> Affects Versions: 2.17.1
> Reporter: Timon H.
> Assignee: Piotr Karwasz
> Priority: Major
> Fix For: 2.19.0
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> 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
> {_}getRequeste{*}d{*}ApiVersion{_}.
> h3. See the Changelog of SLF4J-API 2.0.0-alpha3:
> * The {{getRequesteApiVersion}} method in {{SLF4JServiceProvider}} was
> renamed as getRequeste{*}d{*}ApiVersion. This fixes
> [SLF4J-516|https://jira.qos.ch/browse/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)}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
