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 2009/06/23 23:27:07 UTC

[jira] Resolved: (TIKA-248) No logging in tika-core

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

Jukka Zitting resolved TIKA-248.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 0.4

Removed all logging statements in revision 787830.

Tika now throws exceptions on the kinds of configuration errors that were previously handled by logging warnings. This may break some deployments, but in general I think this trouble is worth the effort of fixing such broken configurations.

> No logging in tika-core
> -----------------------
>
>                 Key: TIKA-248
>                 URL: https://issues.apache.org/jira/browse/TIKA-248
>             Project: Tika
>          Issue Type: Improvement
>          Components: general
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 0.4
>
>
> As discussed on the mailing list, it would make things simpler if the Tika core didn't log anything and thus had no logging dependencies.

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