[TIKA-3842] Revert slf4j core back to 1.x?

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.5.0
• Fix Version/s: 2.5.0
• Assignee: Unassigned
• Reporter: Tim Allison
• Created: 29/Aug/22 16:12
• Updated: 20/Sep/22 10:35
• Resolved: 20/Sep/22 10:35

Description

We're now getting warnings after the upgrade from slf4j 1.x to 2.x:

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.

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?