[
https://issues.apache.org/jira/browse/TIKA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796251#comment-16796251
]
Konstantin Gribov commented on TIKA-2566:
-----------------------------------------
[[email protected]], why do you prefer log4j (which is implementation first
of all) instead of thin facade (slf4j)? Log4j 1.2 and 2.x are good as
implementation (like in tika-batch, tika-app, tika-server and tika-eval) but as
library dependency seems much less preferable even to commons-logging/jcl
(which is both facade and impl in one package) to me.
Or I misunderstood you and you actually suggest to use log4j2-api? I personally
prefer slf4j-api for its stability and wide adoption. Only known major issue
with it is JPMS support (because of static binding approach used in 1.7.x) but
they are going to fix it in 1.8.x branch without breaking API.
> Move logging in tika-core to log4j via slf4j as we do in the rest of Tika
> -------------------------------------------------------------------------
>
> Key: TIKA-2566
> URL: https://issues.apache.org/jira/browse/TIKA-2566
> Project: Tika
> Issue Type: Sub-task
> Reporter: Tim Allison
> Priority: Minor
> Fix For: 2.0.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
