[
https://issues.apache.org/jira/browse/TIKA-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071669#comment-13071669
]
Nick Burch commented on TIKA-686:
---------------------------------
I'd personally not be in favour of having lots of Tika parser jars - I think it
would make things much more complicated, and lead to confusion when people
accidentally missed one out
Instead, is it not better to have parsers log but then bow out when they can't
find their dependencies? That way, if you don't want to parse the microsoft
office formats you ditch the POI dependencies, keep the standard Tika parser
Jar, ignore the warning and you're away
> Split tika-parsers into separate components
> -------------------------------------------
>
> Key: TIKA-686
> URL: https://issues.apache.org/jira/browse/TIKA-686
> Project: Tika
> Issue Type: Wish
> Components: parser
> Affects Versions: 0.9
> Reporter: Christopher Currie
> Priority: Minor
>
> The email thread [1] from two years ago that led to splitting Tika into
> separate components also suggested splitting tika-parsers into separate
> components based on dependencies. This would be extremely useful, especially
> in cases where a given parser has no dependencies beyond tika-core. Please
> consider refactoring the parsers into separate components for 1.0.
> [1] http://markmail.org/message/tavirkqhn6r2szrz
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
