[
https://issues.apache.org/jira/browse/TIKA-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341529#comment-14341529
]
Hudson commented on TIKA-1558:
------------------------------
SUCCESS: Integrated in tika-trunk-jdk1.7 #513 (See
[https://builds.apache.org/job/tika-trunk-jdk1.7/513/])
Start on unit testing for the new TIKA-1558 style parser blacklisting (nick:
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1662927)
* /tika/trunk/tika-parsers/src/test/java/org/apache/tika/config
*
/tika/trunk/tika-parsers/src/test/java/org/apache/tika/config/TikaParserConfigTest.java
* /tika/trunk/tika-parsers/src/test/resources/org/apache/tika/config
*
/tika/trunk/tika-parsers/src/test/resources/org/apache/tika/config/TIKA-1558-blacklist.xml
> Create a Parser Blacklist
> -------------------------
>
> Key: TIKA-1558
> URL: https://issues.apache.org/jira/browse/TIKA-1558
> Project: Tika
> Issue Type: New Feature
> Reporter: Tyler Palsulich
> Assignee: Tyler Palsulich
> Fix For: 1.8
>
>
> As talked about in TIKA-1555 and TIKA-1557, it would be nice to be able to
> disable Parsers without pulling their dependencies out. In some cases (e.g.
> disable all ExternalParsers), there may not be an easy way to exclude the
> dependencies via Maven.
> So, an initial design would be to include another file like
> {{META-INF/services/org.apache.tika.parser.Parser.blacklist}}. We create a
> new method {{ServiceLoader#loadServiceProviderBlacklist}}. Then, in
> {{ServiceLoader#loadServiceProviders}}, we remove all elements of the list
> that are assignable to an element in
> {{ServiceLoader#loadServiceProviderBlacklist}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
