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.
Thoughts?
- Bob
