[
https://issues.apache.org/jira/browse/TIKA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797354#comment-16797354
]
Konstantin Gribov commented on TIKA-2566:
-----------------------------------------
Just to clarify which option you propose:
1. use slf4j-api in tika-core; slf4j-api with bridges in tika-parsers and
log4j:1.x or log4j-core:2.x as implementation in tika-app etc;
2. use log4j-api:2.x in tika-core, log4j-api:2.x with bridges (slf4j, jul & jcl
to log4j2-api) in tika-parser and log4j-core:2.x as implementation;
3. use log4j-api:2.x in tika-core/tika-parsers; force user to configure logging
deps correctly to use tika-parsers and use log4j-core:2.x as implementation in
tika-app etc?
Option 1 is what I suggested initially in TIKA-2245 and as currently in master.
Option 2 is similar but seems to be more complex since we will still have
slf4j-api, bridge for commons-logging/jcl, bridge for JUL and bridge for slf4j.
Option 3 is less preferable since it requires downstream user to add all
bridges manually, is error-prone and could be a bit fragile.
My preference in this case is to use option 1 since its logical improvement
from current status quo (JUL in tika-core and slf4j+jul-to-slf4j+jcl-over-slf4j
in tika-parsers).
Then downstream user can use:
- log4j 1.x: add log4j:1.x and slf4j-log4j12;
- logback-classic: just add logback-classic;
- log4j 2.x: add log4j-api, log4j-core, log4j-slf4j-impl (slf4j bridge),
log4j-jcl (commons-logging/jcl bridge), log4j-jul (JUL bridge) and exclude
jul-to-slf4j and jcl-over-slf4j.
> 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)
