[
https://issues.apache.org/jira/browse/LOG4J2-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393182#comment-17393182
]
Gary D. Gregory commented on LOG4J2-3133:
-----------------------------------------
Not that Slf4j happily breaks binary compatibility from release to release
without a mention. This has happened several times over the years.
> The slf4j (1.7) implementation is missing some expected methods
> ---------------------------------------------------------------
>
> Key: LOG4J2-3133
> URL: https://issues.apache.org/jira/browse/LOG4J2-3133
> Project: Log4j 2
> Issue Type: Bug
> Components: SLF4J Bridge
> Affects Versions: 2.14.1
> Reporter: Carter Kozak
> Assignee: Carter Kozak
> Priority: Major
> Fix For: 2.15.0
>
>
> The following are missing, and result in linker warnings:
> StaticMDCBinder.getSingleton(): StaticMDCBinder
> StaticMarkerBinder.getSingleton(): StaticMarkerBinder
> This isn't a problem unless you're linting for linkage issues, at runtime the
> error is caught and the singleton field is used directly. We might as well
> avoid exceptions on initialization and support the preferred mechanisms.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
