[
https://issues.apache.org/jira/browse/TIKA-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298345#comment-17298345
]
Konstantin Gribov commented on TIKA-3312:
-----------------------------------------
[~tallison], in that case I think it could safely go into tika-server-core
since it's already end-user runnable application. What do you think about
extracting a module with just a bunch of runtime deps and configs for all cli
tools?
> Support Log4j2 jar in Tika-app.jar
> ----------------------------------
>
> Key: TIKA-3312
> URL: https://issues.apache.org/jira/browse/TIKA-3312
> Project: Tika
> Issue Type: Improvement
> Affects Versions: 1.22, 1.24.1
> Reporter: Charushila Nanekar
> Priority: Critical
>
> Latest version of Tika-app is using older version of Log4j jar which cause an
> issue when Tika-app get integrated with other 3rd Party Application which
> using latest log4j 2 jar.
> Additionally, Apache Log4j 2 is an upgrade to Log4j that provides significant
> improvements over its predecessor.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
