So there seems to be a pretty good consensus forming around moving the sources but some differing opinions on where to put shared parser code.
tika-parser-commons- Pros: We would be able to keep from adding another dependency to the tika-core project. Cons: All parsers would then require an additional dependency on the tika-parser-commons artifact. tika-core Pros: Less hierarchy since all parsers would still just depend on tika-core Cons: Opens the door for tika-core to grow in source and external dependencies. Let me know if I've missed anything. I think I'd be leaning closer to wanting to put the code in tika-core to limit the hierarchy but I could be swayed if there's strong evidence that tika-cores dependencies would start ballooning. - Bob On Mon, Dec 14, 2015 at 10:43 AM, Nick Burch <n...@apache.org> wrote: > On 14/12/15 16:26, Ray Gauss wrote: > >> I'd vote for a tiki-parser-common(s) artifact for common util classes and >> dependencies. >> > > That would make sense to me > > Nick >
