Return-Path: Delivered-To: apmail-repository-archive@www.apache.org Received: (qmail 98723 invoked from network); 7 Feb 2009 08:54:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Feb 2009 08:54:26 -0000 Received: (qmail 9116 invoked by uid 500); 7 Feb 2009 08:54:26 -0000 Delivered-To: apmail-repository-archive@apache.org Received: (qmail 8994 invoked by uid 500); 7 Feb 2009 08:54:25 -0000 Mailing-List: contact repository-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: repository@apache.org List-Id: Delivered-To: mailing list repository@apache.org Received: (qmail 8985 invoked by uid 99); 7 Feb 2009 08:54:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 07 Feb 2009 00:54:25 -0800 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.220.10 as permitted sender) Received: from [209.85.220.10] (HELO mail-fx0-f10.google.com) (209.85.220.10) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 07 Feb 2009 08:54:17 +0000 Received: by fxm3 with SMTP id 3so1489145fxm.17 for ; Sat, 07 Feb 2009 00:53:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=+8tRq4+zMJUMapUsnL/5gmYOPKvUvojHUVPV4f3f5Mw=; b=XmC+evz6+UvzRR45huipuV5eD5RJDrJXUW8POBE3p3hWm3kHmZESr5F9Ty9wX0kGFQ IXUzfujfbpGq6iTd5yjxQsscVLBfJ2eXLF7Uy2UgPYTCCts1yjaXlK+iJwX/DNfpVXfT C6qQzpdQUroPJKiO5LNhnMbiUqEQjjnGXJ/fM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=EZ3U00ZFgbVwU2OKgoZg0RvYZWNBifsx6/CIQealXgBVYfbqQW4P7wAqF+8Sa9S/aO I3S8XFr9AZLG/YJ6ptujEf8Ra1ZSWVtnmJc6qN8qiC70v4R9Ca4zgfJFxwCHoORsXy/N xmLH+RNuRt+6sVpwvZoHjDO62CMHSs4ntqx6o= MIME-Version: 1.0 Received: by 10.181.60.14 with SMTP id n14mr277342bkk.23.1233996836450; Sat, 07 Feb 2009 00:53:56 -0800 (PST) In-Reply-To: <1a5b6c410902062203v2dda732aw2f62645ac61da0e6@mail.gmail.com> References: <510143ac0902061554g4acd5098sf833ac1d54c8f95f@mail.gmail.com> <1a5b6c410902062203v2dda732aw2f62645ac61da0e6@mail.gmail.com> Date: Sat, 7 Feb 2009 09:53:56 +0100 Message-ID: <510143ac0902070053s7fb67663y1f9ea303812d2ec6@mail.gmail.com> Subject: Re: Removing an accidental release from the central From: Jukka Zitting To: repository@apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, On Sat, Feb 7, 2009 at 7:03 AM, Carlos Sanchez wrote: > another thing you have to consider is that it also got propagated to > the mirrors. What would be the problem leaving it there? are you > making a new release any time soon? This is an experimental component that one of our committers forked from code in the Jackrabbit sandbox. We will probably never make an official release of this code, at least not using this artifactId. The deployed artifacts are unsigned and the source jar even contains code that was never committed to Apache svn. If artifacts like this appeared in www.apache.org/dist, they'd be removed as a breach of Apache policy. In practice it's not that big a problem to have some extra files within org/apache/jackrabbit on the central repository, but in principle it's not very good that an individual mistake can cause that directory to contain material that has not been approved by the Jackrabbit PMC. BR, Jukka Zitting