jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Guggisberg <stefan.guggisb...@gmail.com>
Subject Re: Jackrabbit dependencies
Date Thu, 03 Feb 2011 11:10:17 GMT
On Thu, Feb 3, 2011 at 11:54 AM, Jukka Zitting <jzitting@adobe.com> wrote:
> Hi,
> On 02/03/2011 11:34 AM, Stefan Guggisberg wrote:
>> do you have any convincing use case for keeping rome in jackrabbit
>> core?
> Not really. It might be useful for something like a feed aggregator
> application, but then again such an application would likely store feeds
> as fine-grained JCR content instead of Atom/RSS files.
>> rome has a dependency on jdom. jdom used to cause class loading
>> issues in the past.
> Agreed, jdom is troublesome.
>> i'd rather prefer to not clutter up jackrabbit core with useless
>> dependencies.
> What do you think of the idea of moving the tika-parsers dependency from
> jackrabbit-core to the deployment packages like jackrabbit-webapp and
> jackrabbit-jca? Tika is intentionally split into tika-core and tika-parsers
> to allow such a setup.

yes, that's probably a good idea. however, i stil think it would be worthwhile
getting rid of unnecessary (transitive) dependencies and making sensible
decisions when adding new dependencies.


> --
> Jukka Zitting

View raw message