[
https://issues.apache.org/jira/browse/TIKA-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905363#comment-14905363
]
Hudson commented on TIKA-1657:
------------------------------
UNSTABLE: Integrated in tika-trunk-jdk1.7 #853 (See
[https://builds.apache.org/job/tika-trunk-jdk1.7/853/])
TIKA-1657 Update the example of dumping a Tika Config to support different
output modes, for Translators and Detectors (nick:
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1704934)
*
/tika/trunk/tika-core/src/main/java/org/apache/tika/language/translate/DefaultTranslator.java
*
/tika/trunk/tika-example/src/main/java/org/apache/tika/example/DumpTikaConfigExample.java
*
/tika/trunk/tika-example/src/test/java/org/apache/tika/example/DumpTikaConfigExampleTest.java
> 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.11
>
> 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)
