You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by Jukka Zitting <ju...@gmail.com> on 2007/08/17 21:32:02 UTC

Tika dependency hell

Hi,

The current early version of Tika already pulls in 21 dependency jars
totalling over 15 megabytes. The dependencies include two logging
frameworks and three XML frameworks. A number of the primary
dependencies use different versions of the same transitive
dependencies.

Any ideas on how to best manage the dependency space? I really
wouldn't like to start playing class loading games or leveraging
higher-level stuff like OSGi.

BR,

Jukka Zitting

Re: Tika dependency hell

Posted by Bertrand Delacretaz <bd...@apache.org>.
On 8/17/07, Jukka Zitting <ju...@gmail.com> wrote:

> ....I really
> wouldn't like to start playing class loading games or leveraging
> higher-level stuff like OSGi....

One option might be build-time selection of which dependencies are
included, for example by breaking the code into Maven modules, and
selectively building them using Maven profiles.

Apart from that, I have a feeling that clever classloading might be
required pretty soon: an important goal of Tika (IMHO) is to be able
to reuse the many "format libraries" that are out there, and they
won't change their dependencies for us.

If there was a way to use something like a mini-OSGI internally in
Tika, with little or no impact on the code that uses Tika, that might
be the best option. I don't have a concrete proposal at this point,
though.

-Bertrand

Re: Tika dependency hell

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On 8/22/07, Sami Siren <ss...@gmail.com> wrote:
> I know I am not answering your question really, but to get application
> dependencies smaller (in some cases) one could split the code into
> smaller modules (one for each format) so if one only needs parsing for
> word one would depend on a module that provides the functionality (and
> transitive dependencies required) for that format.
>
> iwe could also introduce format-all that aggregates all supported
> formats if that's what user is after.

In principle I'd rather go for a one-size-fits-all solution to
maximize simplicity, but I guess there will be many use cases where a
more trimmed down set of dependencies makes more sense.

Perhaps, as suggested by Bertrand, we should also come up with some
class loading trickery along such module boundaries to better handle
conflicting dependencies etc. Sounds scary though...

BR,

Jukka Zitting

Re: Tika dependency hell

Posted by Sami Siren <ss...@gmail.com>.
hi,

I know I am not answering your question really, but to get application
dependencies smaller (in some cases) one could split the code into
smaller modules (one for each format) so if one only needs parsing for
word one would depend on a module that provides the functionality (and
transitive dependencies required) for that format.

iwe could also introduce format-all that aggregates all supported
formats if that's what user is after.

--
 Sami Siren



2007/8/17, Jukka Zitting <ju...@gmail.com>:
> Hi,
>
> The current early version of Tika already pulls in 21 dependency jars
> totalling over 15 megabytes. The dependencies include two logging
> frameworks and three XML frameworks. A number of the primary
> dependencies use different versions of the same transitive
> dependencies.
>
> Any ideas on how to best manage the dependency space? I really
> wouldn't like to start playing class loading games or leveraging
> higher-level stuff like OSGi.
>
> BR,
>
> Jukka Zitting
>