[ https://issues.apache.org/jira/browse/TIKA-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829929#comment-15829929 ]
Konstantin Gribov commented on TIKA-2245: ----------------------------------------- [~talli...@mitre.org], [~mcaruanagalizia], we can't get rid of slf4j-api, since many upstream parsers depends on them (rome, netcdf, grib to name some). I didn't see log4j in {{tika-parsers}} deps and it's better to avoid if no upstream deps use its api directly. I personally prefer parsers to use slf4j-api but current status quo is that parser often use same logging framework as its upstream dependency does. > 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)