>> example is the org.apache.tika.parser.utils.CommonsDigester. Could classes >> like this be moved into tika-core? Y, I was not happy with the split I did with that, but I wanted to avoid adding a dependency on commons-codec into core. What do others think...another 180k into the core jar?
-----Original Message----- From: Bob Paulin [mailto:b...@bobpaulin.com] Sent: Monday, December 14, 2015 9:16 AM To: dev@tika.apache.org Subject: Re: Tika 2.0 Source in Modules or tika-parser Answers inline On 12/14/2015 5:24 AM, Nick Burch wrote: > On Sun, 13 Dec 2015, Bob Paulin wrote: >> So in short >> >> Source in tika-parser >> Dependencies managed in tika-parser and copied to module >> >> Source in Modules >> Dependencies managed in modules and consolidated via maven shade >> plugin. Conflicting dependencies managed by maven. > > IIRC there are some util / parent classes in the tika parsers module > which many different parsers need. Where would those end up? Good question. This would only apply if the sources were moved to the modules. If the parent classes only applied to specific parsers they would move into the modules supporting those parsers. However there are more broad examples where this would not make sense. I think one example is the org.apache.tika.parser.utils.CommonsDigester. Could classes like this be moved into tika-core? Another option could be forming a tika-parser-util class but there doesn't seem to be a lot of classes that would fall under that module. > Thanks > Nick > Thanks, - Bob
