On Mon, May 25, 2015 at 4:05 PM, Nick Burch <apa...@gagravarr.org> wrote:
> On Mon, 25 May 2015, Mattmann, Chris A (3980) wrote: > >> ExternalParser is way broke. I have some patches that somewhat fix it, >> but in doing so, I realized, why not just use commons-exec? I realize that >> this is another dependency into core, but commons-exec simplifies a lot of >> the stuff that's broke with ExternalParser (reading its streams, for one). >> > > 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? Tyler