[
https://issues.apache.org/jira/browse/TIKA-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341555#comment-14341555
]
Hudson commented on TIKA-1509:
------------------------------
SUCCESS: Integrated in tika-trunk-jdk1.7 #514 (See
[https://builds.apache.org/job/tika-trunk-jdk1.7/514/])
TIKA-1558 Support excluding (blacklisting) parsers from config, so you can use
DefaultParser for all except certain parsers. Also supports child parsers of a
composite parser from config, towards TIKA-1509 (nick:
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1662940)
* /tika/trunk/tika-core/src/main/java/org/apache/tika/config/TikaConfig.java
*
/tika/trunk/tika-core/src/main/java/org/apache/tika/parser/CompositeParser.java
* /tika/trunk/tika-core/src/main/java/org/apache/tika/parser/DefaultParser.java
*
/tika/trunk/tika-parsers/src/test/java/org/apache/tika/config/TikaParserConfigTest.java
> Create configurable strategies for composite parsers
> ----------------------------------------------------
>
> Key: TIKA-1509
> URL: https://issues.apache.org/jira/browse/TIKA-1509
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
>
> Several parsers can handle the same mime type, and we are currently ordering
> which parser is chosen (roughly) by the alphabetic order of the parser class
> name.
> Let's allow users to configure strategies for picking parsers.
> See and contribute to full discussion here:
> http://wiki.apache.org/tika/CompositeParserDiscussion
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
