jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Meschberger <fmesc...@gmail.com>
Subject Re: JCR Commons or Commons JCR
Date Sun, 28 Sep 2008 20:45:22 GMT

I agree, that the Apache Jackrabbit project is really a collection
multiple projects: JCR-170/283 RI, SPI, JCR-RMI, OCM and JCR-Commons. As
such we already live in a world where "Jackrabbit" means the RI and the
Apache Project "umbrella".

I think we should acknowledge this and act accordingly ;-)

Therefore, I think the natural location for such a commons library is
the Apache Jackrabbit project -- as a user I would look for such a
library at jackrabbit.apache.org and not at jakarta.apache.org.


Jukka Zitting schrieb:
> Hi,
> A notable part of our codebase is stuff that works on top of the JCR
> API without a direct relation to the Jackrabbit repository
> implementation. Having this code in Jackrabbit is one key driver for
> example in the desire to make our release process more componentized.
> It also makes the "What is Jackrabbit?" question harder to answer and
> looks weird in JCR client applications that have a direct dependency
> to "Jackrabbit" even if it's just jackrabbit-jcr-commons.
> David just brought up the idea of splitting such general purpose JCR
> code out of Jackrabbit. One way to do it would be to create a "JCR
> Commons" subproject within Jackrabbit, and another would be to propose
> starting a "Commons JCR" component in Apache Commons.
> BR,
> Jukka Zitting

View raw message