[
https://issues.apache.org/jira/browse/TIKA-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew Caruana Galizia updated TIKA-2245:
------------------------------------------
Description:
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.
was:
Tika parsers sometimes use Log4j's Logger and the JUL (java.util.logging)
Logger. I will happily make a pull request to standardise on the latter, as I
believe users shouldn't be forced to use a third-party library.
It would be better to standardise on the lowest common denominator and leave
users free to use their own bridge, for example JUL-to-log4j or whatever they
want.
Summary: Standardise logging (was: Standardise on java.util.Logging)
> 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)
