[
https://issues.apache.org/jira/browse/LOG4J2-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16353335#comment-16353335
]
Ralph Goers commented on LOG4J2-2241:
-------------------------------------
We really don't have much choice since SLF4J changed the binding contract and
implementations are no longer compatible with older versions of SLF4J, which is
a real problem for a framework like Log4j that tries to be as compatible with
as much as possible.
> log4j-slf4j-impl does not provide slf4j with the service provider with Java 9
> -----------------------------------------------------------------------------
>
> Key: LOG4J2-2241
> URL: https://issues.apache.org/jira/browse/LOG4J2-2241
> Project: Log4j 2
> Issue Type: Bug
> Components: SLF4J Bridge
> Affects Versions: 2.10.0
> Reporter: Joshua Popoff
> Priority: Blocker
>
> log4j-slf4j-impl does notÂ
> {noformat}
> provides org.slf4j.spi.SLF4JServiceProvider with
> org.apache.logging.slf4j.SLF4JServiceProvider;{noformat}
> (due to no module-info.java, and only an automatic module name, in the
> log4j-slf4j-impl project.
> When ran:
> {noformat}
> SLF4J: No SLF4J providers were found.
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#noProviders for further details.
> SLF4J: Class path contains SLF4J bindings targeting slf4j-api versions prior
> to 1.8.
> SLF4J: Ignoring binding found at
> [jar:file://[redacted]/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#ignoredBindings for an explanation.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
