[ https://issues.apache.org/jira/browse/TIKA-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333394#comment-14333394 ]
Chris A. Mattmann commented on TIKA-1558: ----------------------------------------- I agree that longer term we should move more to a config file, but there is a lot of work that needs to be done between now and then. This is a good interim solution and the code can keep evolving, so if someone comes up with a better patch by all means. Nick's solution was great; we now have a solution that Tyler added; and later maybe we can trump both of them with the config file. > 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)