Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of fmeschbe@gmail.com designates
 64.233.182.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=NmivpGhlEvWfg9wh85Ma5ilVZbqdXY1JHyiRNlmc/MlOQt73G+ZxzCtQyucW/Dh7t4
         +MooqFMLmwWjdGozzs+S0IjZwMP037VohVTYmVinR3YuX3O0UWB3TtLEbZRf77ysMdI9
         ZEOhiHSSK8oCRiz0PpxZoNly4kSQovCiQThZs=
Message-ID: <48DFECE2.2010403@gmail.com>
Date: Sun, 28 Sep 2008 22:45:22 +0200
From: Felix Meschberger <fmeschbe@gmail.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080501)
MIME-Version: 1.0
To: dev@jackrabbit.apache.org
Subject: Re: JCR Commons or Commons JCR
References: <510143ac0809260848v7abb3df7u700e08d97487676f@mail.gmail.com>
In-Reply-To: <510143ac0809260848v7abb3df7u700e08d97487676f@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

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.

Regards
Felix

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
>