[jira] [Commented] (TIKA-2566) Move logging in tika-core to log4j via slf4j as we do in the rest of Tika
[ 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: - [~talli...@apache.org], 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)
[jira] [Commented] (TIKA-2566) Move logging in tika-core to log4j via slf4j as we do in the rest of Tika
[ https://issues.apache.org/jira/browse/TIKA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796262#comment-16796262 ] Konstantin Gribov commented on TIKA-2566: - JFYI: https://www.slf4j.org/faq.html#changesInVersion18 states that "There are no client facing API changes in 1.8.x". It has version 1.8.0-beta4 right now in central but I hope it would be released soon. > 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)
[jira] [Commented] (TIKA-2245) Standardise logging
[ https://issues.apache.org/jira/browse/TIKA-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796242#comment-16796242 ] Konstantin Gribov commented on TIKA-2245: - [~talli...@apache.org], slf4j-api is quite stable from API perspective, so it should be compatible with other 1.7.x versions. But it's better to use same slf4j-api and implementation versions as SPI compatibility is not guaranteed. Sorry for belated answer. > 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 >Assignee: Konstantin Gribov >Priority: Major > Labels: logging > Fix For: 1.15 > > > 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 (v7.6.3#76005)
[jira] [Commented] (TIKA-2840) windows batch file not detected
[ https://issues.apache.org/jira/browse/TIKA-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796134#comment-16796134 ] chandra commented on TIKA-2840: --- any update on this issue would be appreciated thank you CP > windows batch file not detected > --- > > Key: TIKA-2840 > URL: https://issues.apache.org/jira/browse/TIKA-2840 > Project: Tika > Issue Type: Bug > Components: core >Affects Versions: 1.20 > Environment: tika core not detecting windows batch file when its > renamed with .txt, it results in mime type text/plain >Reporter: chandra >Priority: Major > Attachments: test.txt > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
