tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (TIKA-28) Rename config.xml to tika-config.xml or similar.
Date Mon, 24 Sep 2007 21:30:50 GMT

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

Chris A. Mattmann resolved TIKA-28.

    Resolution: Fixed

- renamed config.xml to tika-config.xml
- updated unit test

> Rename config.xml to tika-config.xml or similar.
> ------------------------------------------------
>                 Key: TIKA-28
>                 URL: https://issues.apache.org/jira/browse/TIKA-28
>             Project: Tika
>          Issue Type: Improvement
>          Components: general
>    Affects Versions: 0.1-incubator
>            Reporter: Keith R. Bennett
>            Assignee: Chris A. Mattmann
>             Fix For: 0.1-incubator
> Although we may be rethinking our configuration options over the longer term, it would
be helpful in the short term to rename config.xml to tika-config.xml, or some other name that
would not be as general as config.xml.
> The tika jar file will usually be one of many jar files included in an application, and
its current location in the default package means that a different config.xml file might be
found in the classpath before the Tika one.

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

View raw message