jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra" <tobias.bocane...@day.com>
Subject Re: JCR Commons or Commons JCR
Date Sun, 28 Sep 2008 22:50:01 GMT
On 9/28/08, Felix Meschberger <fmeschbe@gmail.com> wrote:
> Hi,
>
>  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.
i don't :-) as i would not look for commons-fileupload or commons-el
to be in tomcat (might be a bit far fetched :-). however, i think it
would help to drive JCR as standard if there would be a commons-jcr.
and for that alone it's worth it.

regards, toby

>  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.
>  >
>  > WDYT?
>  >
>  > BR,
>  >
>  > Jukka Zitting
>  >
>

Mime
View raw message