Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 35156 invoked from network); 28 Sep 2008 20:18:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Sep 2008 20:18:08 -0000 Received: (qmail 66230 invoked by uid 500); 28 Sep 2008 20:18:05 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 66198 invoked by uid 500); 28 Sep 2008 20:18:05 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 66187 invoked by uid 99); 28 Sep 2008 20:18:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Sep 2008 13:18:05 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of tripod@day.com designates 207.126.148.181 as permitted sender) Received: from [207.126.148.181] (HELO eu3sys201aog001.obsmtp.com) (207.126.148.181) by apache.org (qpsmtpd/0.29) with SMTP; Sun, 28 Sep 2008 20:17:04 +0000 Received: from source ([209.85.146.176]) by eu3sys201aob001.postini.com ([207.126.154.11]) with SMTP; Sun, 28 Sep 2008 20:17:34 UTC Received: by wa-out-1112.google.com with SMTP id k34so1060995wah.25 for ; Sun, 28 Sep 2008 13:17:33 -0700 (PDT) Received: by 10.114.151.13 with SMTP id y13mr4651460wad.148.1222633053573; Sun, 28 Sep 2008 13:17:33 -0700 (PDT) Received: by 10.114.254.12 with HTTP; Sun, 28 Sep 2008 13:17:33 -0700 (PDT) Message-ID: Date: Sun, 28 Sep 2008 22:17:33 +0200 From: "Tobias Bocanegra" Sender: tripod@day.com To: dev@jackrabbit.apache.org Subject: Re: JCR Commons or Commons JCR In-Reply-To: <510143ac0809260848v7abb3df7u700e08d97487676f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <510143ac0809260848v7abb3df7u700e08d97487676f@mail.gmail.com> X-Google-Sender-Auth: 406e819548de6d53 X-Virus-Checked: Checked by ClamAV on apache.org On 9/26/08, Jukka Zitting wrote: > 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? i find this a very good idea. i would love to have all the helpers and tools that operate directly on jcr and not the jackrabbit-api in a commons-jcr project. having it outside of jackrabbit is surely the longtime goal - but some code of jackrabbit core depends on it, and i fear that a new commons-jcr project would be less controllable if not maintained by jackrabbit devs. otoh it wold certainly push jcr more to the community and make it even more visible. so what about 'incubate' a jcr-commons (org.apache.jackrabbit.commons.jcr.*) within jackrabbit and shell out all important peaces, and then once released as jackrabbit project apply for a subproject within apache-commons ? regards, toby