[
https://issues.apache.org/jira/browse/TIKA-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071769#comment-13071769
]
Ken Krugler commented on TIKA-686:
----------------------------------
@Nick - my thought that that we'd have a tika-parsers that had dependencies on
all of the parsers, so if you want them all you'd just have to have a
dependency on that.
This would be similar to what Jukka talked about, where tika-parsers is a
composite that brings all of the individual parsers together.
Though if you're not using a dependency management system, that would make
things harder.
@Jukka - what are you concerns about "an explosion of dependencies", if that
was the case.
@Jukka - What is your assessment of the current state of affairs in Tika, for
gracefully handling missing dependencies? I haven't tracked recent changes, but
I thought that we'd run into a new cause of failure when a required library was
excluded.
> 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
