You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (Jira)" <ji...@apache.org> on 2022/08/29 16:13:00 UTC
[jira] [Updated] (TIKA-3842) Revert slf4j core back to 1.x?
[ https://issues.apache.org/jira/browse/TIKA-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Allison updated TIKA-3842:
------------------------------
Description:
We're now getting warnings after the upgrade from slf4j 1.x to 2.x:
{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:/home/tallison/.m2/repository/org/apache/logging/log4j/log4j-slf4j-impl/2.18.0/log4j-slf4j-impl-2.18.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#ignoredBindings for an explanation.
{noformat}
These are explained here: https://www.slf4j.org/codes.html with some further explanation here: https://www.slf4j.org/faq.html#changesInVersion200
I think the underlying issue is that there isn't yet a log4j2 bridge for slf4j 2.x: https://issues.apache.org/jira/browse/LOG4J2-3139
Should we revert slf4j back to 1.x until this is resolved?
was:
We're now getting warning after the upgrade from slf4j 1.x to 2.x:
{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:/home/tallison/.m2/repository/org/apache/logging/log4j/log4j-slf4j-impl/2.18.0/log4j-slf4j-impl-2.18.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#ignoredBindings for an explanation.
{noformat}
These are explained here: https://www.slf4j.org/codes.html with some further explanation here: https://www.slf4j.org/faq.html#changesInVersion200
I think the underlying issue is that there isn't yet a log4j2 bridge for slf4j 2.x: https://issues.apache.org/jira/browse/LOG4J2-3139
Should we revert slf4j back to 1.x until this is resolved?
> Revert slf4j core back to 1.x?
> ------------------------------
>
> Key: TIKA-3842
> URL: https://issues.apache.org/jira/browse/TIKA-3842
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
> Priority: Minor
>
> We're now getting warnings after the upgrade from slf4j 1.x to 2.x:
> {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:/home/tallison/.m2/repository/org/apache/logging/log4j/log4j-slf4j-impl/2.18.0/log4j-slf4j-impl-2.18.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#ignoredBindings for an explanation.
> {noformat}
> These are explained here: https://www.slf4j.org/codes.html with some further explanation here: https://www.slf4j.org/faq.html#changesInVersion200
> I think the underlying issue is that there isn't yet a log4j2 bridge for slf4j 2.x: https://issues.apache.org/jira/browse/LOG4J2-3139
> Should we revert slf4j back to 1.x until this is resolved?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)