[
https://issues.apache.org/jira/browse/TIKA-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830244#comment-15830244
]
Konstantin Gribov commented on TIKA-2245:
-----------------------------------------
[[email protected]], I guess [~mcaruanagalizia] wants just to simplify logger
configuration as downstream user. As a facade {{slf4j}} is currently best
option, and it's designed for such usecases. I don't know how simple is to
configure slf4j in OSGi environment, maybe [~bobpaulin] can add something about
that.
So, I propose to do all logging via {{slf4j-api}}, add {{jul-to-slf4j}},
{{jcl-over-slf4j}} and {{commons-logging-api}} to {{tika-parsers}}
dependencies, exclude {{commons-logging}} from it and recommend users to add
{{slf4j-log4j12}} as default logging dependency (we should avoid adding it
ourselves since it's not library responsibility). It allows user to opt-out and
use {{logback-classic}} + {{log4j-over-slf4j}} if he wants. Alternative way
should also be documented.
If it's OK, I'll push it to master soon.
> Standardise logging
> -------------------
>
> Key: TIKA-2245
> URL: https://issues.apache.org/jira/browse/TIKA-2245
> Project: Tika
> Issue Type: Improvement
> Components: parser
> Affects Versions: 1.14, 1.15
> Reporter: Matthew Caruana Galizia
> Labels: logging
>
> Tika parsers sometimes use Log4j's Logger, sometimes the JUL
> (java.util.logging) Logger and sometimes SLF4j.
> It would be better to standardise on a single facade, for the sake of not
> having to configure multiple loggers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
