On Mon, 25 May 2015, Tyler Palsulich wrote:
Maybe we could push some or all of external parser into the
tika-parsers module, so we don't have to add more dependencies into
core?
What is the argument for having ExternalParser in core? Provide an
easy-to-extend class for downstream users to create their own external
parser?
I can't be certain, as svn blame suggests is was done over 4 yeras ago,
but I've got a feeling we said something like "the other parser abstract
and base classes are in core, and it has no dependencies, so why not put
it in core too". Quite possible there's a comment around that in the list
archives or jira, if someone fancies a few minutes with google to verify!
Nick
