[
https://issues.apache.org/jira/browse/TIKA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426383#comment-17426383
]
Lewis John McGibbney commented on TIKA-3453:
--------------------------------------------
The problem lies in the *_<scope>_* of the [logging
dependencies|https://github.com/apache/tika/blob/main/tika-server/tika-server-core/pom.xml#L129-L139].
{code:xml}
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
<version>${log4j2.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-slf4j-impl</artifactId>
<version>${log4j2.version}</version>
<scope>test</scope>
{code}
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder" Defaulting to
> no-operation (NOP) logger implementation for tika-docker 2.0.0-BETA
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TIKA-3453
> URL: https://issues.apache.org/jira/browse/TIKA-3453
> Project: Tika
> Issue Type: Bug
> Components: docker, server
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Priority: Major
> Fix For: 2.1.1
>
>
> It looks like logging libraries are not being interpreted correctly from Java
> classpath.
> We need logging turned on so we can intercept anomalies.
> Investigating...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
