Hey Konstantin,
Your observation is spot on and also is the reason why there is an
advantage to having separate ones. The bundles are not meant to be used
outside of OSGi. The current tika-bundle has many entries in the
MANIFEST.MF due to the embedded dependencies. We also depend on maven to
Nick,
I see now why it was done: we use `Embed-Dependency` for tika-bundle in 1.x
and for tika-parser-*-bundle in 2.x so it produces fat/uber jar with some
dependencies inlined in them.
This is unsuitable for non-OSGi builds.
So I withdraw my "bright" idea about merging corresponding modules and
On Wed, 29 Mar 2017, Konstantin Gribov wrote:
I've been surprised by such separation, what was the reason to separate
them?
I think partly history (we split in 1.x), partly how the split was done
(osgi folks amongst the most keen), and partly a desire not to have
non-OSGi users getting a
