[
https://issues.apache.org/jira/browse/TIKA-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333400#comment-14333400
]
Uwe Schindler commented on TIKA-1558:
-------------------------------------
Hi,
Lucene uses SPI for its index codecs, so we are familar with SPI. But we have
no problems with "order" of classpath. We just preserve what Java delivers in
Classloader.getResources(). But order is not really important (it was important
for testing in Lucene 4.x, but that's history since last Friday).
We already have a custom TikaConfig class so I am happy to use that. In our
case we would only put the SPI exclusion into our test classpath. But
TikaConfig is also fine.
> 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)
