You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2007/10/07 20:55:50 UTC

[jira] Commented: (TIKA-47) Remove TikaLogger

    [ https://issues.apache.org/jira/browse/TIKA-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532992 ] 

Chris A. Mattmann commented on TIKA-47:
---------------------------------------

+1 here.

Question for you: should we remove the use of Log4J in general as part of this issue and move to JDK logging? So far, Jukka and I are both +1 for JDK logging. Is this acceptable to everyone else? If so, I'd like to propose removing all logging dependencies and changing all logging in Tika to use JDK 1.4 logging, configured with a tika.logging.properties file. What do others think?

> Remove TikaLogger
> -----------------
>
>                 Key: TIKA-47
>                 URL: https://issues.apache.org/jira/browse/TIKA-47
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Jukka Zitting
>            Priority: Minor
>
> The org.apache.tika.log.TikaLogger class is essentially a simple wrapper for Log4J PropertyConfigurator.
> We should remove the class and directly configure Log4J (or whatever logging framework we use) in client code.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.