[
https://issues.apache.org/jira/browse/TIKA-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved TIKA-317.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.7
I committed the proposed patch (revision 911195) and followed up with a change
that makes the default Tika configuration use the Java service provider
mechanism to find all available Parser classes (revision 911225).
With this change you'll no longer need to maintain a custom copy of
tika-config.xml if you want to extend Tika with your own parser classes.
Instead you can just list your parser classes in a
META-INF/services/org.apache.tika.parser.Parser file inside the jar that
contains your extensions.
> Service provider -based Tika configuration
> ------------------------------------------
>
> Key: TIKA-317
> URL: https://issues.apache.org/jira/browse/TIKA-317
> Project: Tika
> Issue Type: Improvement
> Components: parser
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 0.7
>
> Attachments: TIKA-317.patch
>
>
> I'd like to simplify Tika configuration and make it easier to customize by
> pushing the information in tika-config.xml to Parser annotations and Java SPI
> service files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
