[
https://issues.apache.org/jira/browse/LOG4J2-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393249#comment-17393249
]
ASF subversion and git services commented on LOG4J2-3133:
---------------------------------------------------------
Commit cb18f36d762154fafd6edfb5c0838ad7d877561e in logging-log4j2's branch
refs/heads/release-2.x from Carter Kozak
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=cb18f36 ]
LOG4J2-3133: log4j-slf4j-impl provides new singleton accessors from slf4j-api
1.7.14
See
https://github.com/qos-ch/slf4j/commit/ea3cca72cd5a9329a06b788317a17e806ee8acd0
and https://jira.qos.ch/browse/SLF4J-347
> 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: Improvement
> 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)
