I'd vote for a tiki-parser-common(s) artifact for common util classes and dependencies.
> On Dec 14, 2015, at 10:54 AM, Ken Krugler <kkrugler_li...@transpac.com> wrote: > > >> From: Bob Paulin >> Sent: December 13, 2015 7:34:03pm PST >> To: dev@tika.apache.org >> Subject: Tika 2.0 Source in Modules or tika-parser >> >> Hi, >> >> I've committed the first module break out to the tika 2.0 branch and I'd >> like to discuss the possibility of moving the source code from the >> tika-parser projects to the modules. The implementation I committed is >> based on the straw man version I proposed a few months ago which copies the >> class files to the modules. The dependencies are managed in the tika-parser >> project and also copied and embedded into the individual modules. If the >> source were moved to the modules would have there own dependency management. >> Then they could be combine into a single jar (as the current tika-parser >> jar) with the maven shade plugin. Any conflicting versions in 2 separate >> modules would be resolved in the tika-parser via maven. >> >> 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. > > I don't have any experience with moving classes around to create modules, so > my natural inclination is to move the sources. > > As far as shared code, I think moving something like commons-codec into core > (100K) is fine. > > -- Ken > > -------------------------- > Ken Krugler > +1 530-210-6378 > http://www.scaleunlimited.com > custom big data solutions & training > Hadoop, Cascading, Cassandra & Solr > > > > >
