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 2015/10/18 21:44:07 UTC
[jira] [Updated] (TIKA-1657) Allow easier XML serialization of
TikaConfig
[ https://issues.apache.org/jira/browse/TIKA-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated TIKA-1657:
------------------------------------
Fix Version/s: (was: 1.11)
1.12
> Allow easier XML serialization of TikaConfig
> --------------------------------------------
>
> Key: TIKA-1657
> URL: https://issues.apache.org/jira/browse/TIKA-1657
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
> Priority: Minor
> Fix For: 1.12
>
> Attachments: TIKA-1558-blacklist-effective.xml, TIKA-1657v1.patch
>
>
> In TIKA-1418, we added an example for how to dump the config file so that users could easily modify it. I think we should go further and make this an option at the tika-core level with hooks for tika-app and tika-server. I propose adding a main() to TikaConfig that will print the xml config file that Tika is currently using to stdout.
> I'd like to put this into core so that e.g. Solr's DIH users can get by without having to download tika-app separately.
> There's every chance that I've not accounted for issues with dynamic loading etc. Also, I'd be ok with only having this available in tika-app and tika-server if there are good reasons.
> Feedback?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)