[
https://issues.apache.org/jira/browse/TIKA-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17606764#comment-17606764
]
Hudson commented on TIKA-3842:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk8 #805 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/805/])
TIKA-3842 -- upgrade to slf4j 2.x (tallison:
[https://github.com/apache/tika/commit/95ef6583a57c1e79fabd7d971b9da7a4275e0621])
* (edit) CHANGES.txt
* (edit)
tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-microsoft-module/pom.xml
* (edit) tika-pipes/tika-emitters/tika-emitter-kafka/pom.xml
* (edit) tika-pipes/tika-fetchers/tika-fetcher-s3/pom.xml
* (edit) tika-server/tika-server-client/pom.xml
* (edit) tika-langdetect/tika-langdetect-mitll-text/pom.xml
* (edit) tika-pipes/tika-fetchers/tika-fetcher-http/pom.xml
* (edit) tika-parsers/tika-parsers-ml/tika-age-recogniser/pom.xml
* (edit) tika-pipes/tika-pipes-iterators/tika-pipes-iterator-kafka/pom.xml
* (edit) tika-pipes/tika-pipes-iterators/tika-pipes-iterator-s3/pom.xml
* (edit) tika-langdetect/tika-langdetect-lingo24/pom.xml
* (edit) tika-server/tika-server-core/pom.xml
* (edit) tika-pipes/tika-emitters/tika-emitter-solr/pom.xml
* (edit) tika-server/tika-server-standard/pom.xml
* (edit) tika-parsers/tika-parsers-ml/tika-dl/pom.xml
* (edit)
tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-pdf-module/pom.xml
* (edit) tika-core/pom.xml
* (edit) tika-fuzzing/pom.xml
* (edit) tika-eval/tika-eval-app/pom.xml
* (edit) tika-app/pom.xml
* (edit) tika-integration-tests/tika-pipes-kafka-integration-tests/pom.xml
* (edit) tika-parent/pom.xml
* (edit) tika-pipes/tika-emitters/tika-emitter-s3/pom.xml
> Revert slf4j core back to 1.x?
> ------------------------------
>
> Key: TIKA-3842
> URL: https://issues.apache.org/jira/browse/TIKA-3842
> Project: Tika
> Issue Type: Improvement
> Affects Versions: 2.5.0
> 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)
