You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "John Engelke (Jira)" <ji...@apache.org> on 2021/10/11 19:30:00 UTC

[jira] [Created] (TIKA-3568) Tika CLI tightly coupled to Log4J2

John Engelke created TIKA-3568:
----------------------------------

             Summary: Tika CLI tightly coupled to Log4J2
                 Key: TIKA-3568
                 URL: https://issues.apache.org/jira/browse/TIKA-3568
             Project: Tika
          Issue Type: Bug
          Components: app
    Affects Versions: 2.1.1
            Reporter: John Engelke


[https://github.com/apache/tika/blob/7b167915bfcdc015f5e9afc35b3050bca9c1e1c8/tika-app/src/main/java/org/apache/tika/cli/TikaCLI.java#L383] 

TikaCLI directly invokes a Log4J2 API to set the log level when it should be setting the log level using SLF4J, something like ...
{code:java}
System.setProperty(org.slf4j.impl.SimpleLogger.DEFAULT_LOG_LEVEL_KEY, "DEBUG");
{code}
This tightly couples the CLI to Log4J2 and makes it hard to use another logging framework.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)