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/13 11:14:50 UTC

[jira] Resolved: (TIKA-62) Use TikaConfig.getDefaultConfig() instead of a hardcoded config path in TestParsers

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

Jukka Zitting resolved TIKA-62.
-------------------------------

    Resolution: Fixed

Fixed in revision 584386.

> Use TikaConfig.getDefaultConfig() instead of a hardcoded config path in TestParsers
> -----------------------------------------------------------------------------------
>
>                 Key: TIKA-62
>                 URL: https://issues.apache.org/jira/browse/TIKA-62
>             Project: Tika
>          Issue Type: Improvement
>          Components: general
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Trivial
>             Fix For: 0.1-incubator
>
>
> As discussed on the mailing list, hardcoding the path of the tika-config.xml file in TestParsers.java is not a good idea.
> Instead we should use the TikaConfig.getDefaultConfig() method to load the default configuration.

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