[
https://issues.apache.org/jira/browse/TIKA-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072365#comment-13072365
]
Nick Burch commented on TIKA-686:
---------------------------------
Does anyone know of a good resource for how imports, method signatures,
includes etc affect when a missing dependency will trigger a problem?
It's all very well having the Parser constructor try a Class.forName and
throwing a DependencyMissingException or similar, but if we've done something
that means the Parser blows up with a ClassNotFound before the constructor then
that's no help...
> 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
