Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 86183 invoked from network); 8 Aug 2007 09:32:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Aug 2007 09:32:44 -0000 Received: (qmail 62828 invoked by uid 500); 8 Aug 2007 09:32:42 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 62795 invoked by uid 500); 8 Aug 2007 09:32:42 -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 62786 invoked by uid 99); 8 Aug 2007 09:32:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Aug 2007 02:32:42 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jukka.zitting@gmail.com designates 209.85.132.246 as permitted sender) Received: from [209.85.132.246] (HELO an-out-0708.google.com) (209.85.132.246) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Aug 2007 09:32:35 +0000 Received: by an-out-0708.google.com with SMTP id c37so18882anc for ; Wed, 08 Aug 2007 02:32:17 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UVVvh0bPgWdvI0v4R7sDiKnQlawwHzfQO9AIIeY/YGwK2SjDFb7FQuV20ZHnl9maeyFNXXuSQ2xsUkChpXcVaVAWO4Qe3ZN1OEmvWKGOxZ6lLegVCH8+vlRfTBc6838QCpGqEI03g3+0Ri4Bsg9ClpnvEIOnGn0N+EVufPOHxr4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Le0kbrbBDeRmyN07xe6ybjlIqCjjIH8Mz/oiek+zqp7uxUBczEFdJy8eEFJXe5wzieJrnaPBjSpdIbkmiQdjruojuifk5KZnjkTYvOjRxeHtpIxIXZosHnxBI+QyJ95Vk+1gGOe5NuupbkGuAQTNwxJY3V0KY+lgqqIQMyRgDtw= Received: by 10.100.12.18 with SMTP id 18mr1182279anl.1186565537397; Wed, 08 Aug 2007 02:32:17 -0700 (PDT) Received: by 10.100.178.20 with HTTP; Wed, 8 Aug 2007 02:32:17 -0700 (PDT) Message-ID: <510143ac0708080232td32d2w51f2d32635fbce14@mail.gmail.com> Date: Wed, 8 Aug 2007 12:32:17 +0300 From: "Jukka Zitting" To: dev@jackrabbit.apache.org Subject: Re: JCR 2.0 extensions In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <510143ac0708080206n15b6715bq44eecde6aeb04937@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi, On 8/8/07, Christoph Kiehl wrote: > Sounds good. We just need to make sure that those jsr283 interfaces do not > interfere with jsr170 interfaces because some Jackrabbit classes will need to > implement both interfaces. But since jsr283 should be mainly backwards > compatible this shouldn't be a problem. Yep. In case we do ran up with compatibility issues, I think we have a good case to request a change in JSR 283. > Or do you want to start a whole new branch where all jsr170 interfaces > are replaced by jsr283 interfaces? We need to do that eventually, but I'd very much like to push the branch point as far ahead as possible to avoid getting stuck with two parallel actively developed codebases. Ideally we'd release 1.4 and perhaps even 1.5 with early JCR 2.0 features included before dropping JCR 1.0 from svn trunk and focusing on the real JCR 2.0 interfaces for the Jackrabbit 2.0 release. BR, Jukka Zitting