You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2007/10/07 21:19:50 UTC

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

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

Jukka Zitting updated TIKA-47:
------------------------------

    Attachment: TIKA-47.patch

Here's a patch that removes the TikaLogger class and moves the current log4j configuration to src/test/resources and invokes it using the log4j.configuration system property instead of code within TestParsers.

As for switching to JDK logging, I think we can do it (unless anyone objects) but let's have a separate issue for that.

> Remove TikaLogger
> -----------------
>
>                 Key: TIKA-47
>                 URL: https://issues.apache.org/jira/browse/TIKA-47
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Jukka Zitting
>            Assignee: Chris A. Mattmann
>            Priority: Minor
>         Attachments: TIKA-47.patch
>
>
> 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.