Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 12632 invoked from network); 4 Jul 2007 08:10:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Jul 2007 08:10:47 -0000 Received: (qmail 48454 invoked by uid 500); 4 Jul 2007 08:10:50 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 48208 invoked by uid 500); 4 Jul 2007 08:10:49 -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 48199 invoked by uid 99); 4 Jul 2007 08:10:48 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jul 2007 01:10:48 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of bdelacretaz@gmail.com designates 209.85.146.180 as permitted sender) Received: from [209.85.146.180] (HELO wa-out-1112.google.com) (209.85.146.180) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jul 2007 01:10:45 -0700 Received: by wa-out-1112.google.com with SMTP id m34so3379976wag for ; Wed, 04 Jul 2007 01:10:24 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=s1uZnpt+z3Qobk9IM6ym0rlz/goy4tFoseIif4+BmObXmvLyq2m7PdxdY/mvT7Ik9tJerwor0XMRlSpRJZ4HGOjjtmkGKA1VaMQxQM1CaIv2lrZo3mcTs6MdbucvmrCjV0+bs+ZH6r6+px78sdbmAnsDDRWu5SbYBb6yt/IntyM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=KS5FZK9SwSFIBnHCti/5mac9IGgNfB2+js1dywwz9f9D0usRh8GLejMDxAfd2gD3QmpO5T29JsN7wq6EaI1/TkMea2Cl1DnHM4CaU8BhZMxXygqg4fjpoA8ouBf79H0h8Ts9MUAl6M7NyrfRRqno/JPunKVQ5scAvsnyMc88loE= Received: by 10.114.174.2 with SMTP id w2mr6970469wae.1183536624212; Wed, 04 Jul 2007 01:10:24 -0700 (PDT) Received: by 10.114.197.5 with HTTP; Wed, 4 Jul 2007 01:10:24 -0700 (PDT) Message-ID: Date: Wed, 4 Jul 2007 10:10:24 +0200 From: "Bertrand Delacretaz" Sender: bdelacretaz@gmail.com To: dev@jackrabbit.apache.org Subject: Re: JSR-283 TCK? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Google-Sender-Auth: 8da885c4f40e9f2f X-Virus-Checked: Checked by ClamAV on apache.org On 7/4/07, Arje Cahn wrote: > ...I'm not sure whether this has been discussed on the list already, but > what happens to Jackrabbit when the Apache JCP policy proposal gets > voted in and the ASF will no longer accept a JSR-283 TCK? (or is that > not the case..?)... I'll leave it to others to comment on the openness of JSR 170 and 283, but here are some links to give people more context. I assume you refer to the proposal and discussions listed here: http://davanum.wordpress.com/2007/07/03/implementing-jsrs-apache-radical-shift/ Note that the proposal is being rejected in the vote thread: http://thread.gmane.org/gmane.comp.apache.jcp-open/259 And I tend to agree with Roy when he says such decisions belong to the ASF board anyway: http://thread.gmane.org/gmane.comp.apache.jcp-open/259/focus=288 So it doesn't look like the proposal will be accepted as is. I don't mean to flag your question as irrelevant, but just make sure people have the right context to interpret it ;-) -Bertrand