Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5D55610869 for ; Tue, 15 Oct 2013 17:23:58 +0000 (UTC) Received: (qmail 14963 invoked by uid 500); 15 Oct 2013 17:23:55 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 14852 invoked by uid 500); 15 Oct 2013 17:23:54 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 14844 invoked by uid 99); 15 Oct 2013 17:23:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Oct 2013 17:23:53 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates 74.125.82.54 as permitted sender) Received: from [74.125.82.54] (HELO mail-wg0-f54.google.com) (74.125.82.54) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Oct 2013 17:23:46 +0000 Received: by mail-wg0-f54.google.com with SMTP id c11so3378273wgh.9 for ; Tue, 15 Oct 2013 10:23:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=TZD1jo7Elsht9lrtYrC3HCuw2z+jVPXV3NKxNVvMn3w=; b=pEC3EmWS+7KB2RQDnanC7vANxLBk+e6QMjVZ5Uokf9q3//S4Ua2iyU57shJSVaUgKZ FJ2Gqjb2nC/QqIHsuDY/seieZgqf6MvxKFIAupVEJyhlCj2e1KKtRF9y04gYomd+TLJv Ey/7VK6Di0PA1nWYqpVT0MR2UdgOsBv57FxHGkTVyLsgE6NEP68Zoxj/+dLCwJpie+ev SLvuL0iWuDbREv6nDGGYl2Uasjmu17lMElcBNTdUAd0sL3iRr3HpT1sGhZAz816LoTSq 3WFnmOBwv7Px3t4aFk4qmAWVwN9PD2ekD6c2lFmq//qlQi+h1/qQ1Sl5NIvyVwqmKlmd d+vw== MIME-Version: 1.0 X-Received: by 10.180.11.37 with SMTP id n5mr20466143wib.25.1381857806708; Tue, 15 Oct 2013 10:23:26 -0700 (PDT) Received: by 10.194.24.99 with HTTP; Tue, 15 Oct 2013 10:23:26 -0700 (PDT) In-Reply-To: References: <5256C912.6060606@apache.org> <5257C38B.2030504@apache.org> Date: Tue, 15 Oct 2013 18:23:26 +0100 Message-ID: Subject: Re: [DISCUSS] Creating Project for Release Process Testing... From: sebb To: Commons Developers List , gudnabrsam@gmail.com Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On 15 October 2013 17:54, Matt Benson wrote: > We should probably investigate whether Nexus's REST APIs would be of any > use here; seemingly they would make it much more difficult to inadvertently > delete the wrong file(s). I did try to find out about them. Unfortunately they are not documented anywhere public that I could find (and it appears they may not be stable). I did make some progress by recording the GUI, but that is obviously not ideal. > Matt > > > On Tue, Oct 15, 2013 at 11:33 AM, sebb wrote: > >> On 14 October 2013 02:21, Ralph Goers wrote: >> > >> > On Oct 13, 2013, at 4:31 PM, sebb wrote: >> > >> >> Recently, I found that the Maven project RMs don't bother removing >> these. >> >> So the files are released to Maven Central with the rest. >> >> I assume that the Maven Central administrators don't care about the >> >> extra space needed. >> >> >> >> Now ASF source releases must be provided via the ASF mirror system. >> >> There does not seem to be any ruling on whether having additional >> >> copies of the source release elsehere is allowed or not. >> >> >> >> I tried asking on Infra whether source releases should only be >> >> published to the ASF mirror system, but got no answer. >> >> Perhaps someone else would like to try? >> >> >> >> It would obviously be a lot easier if the Nexus directory did not have >> >> to be purged of these files, as this has to be carefully co-ordinated >> >> with copying the files for the ASF mirror SVN repo. >> > >> > Whether they have to be removed or not as a user I find them being >> published to Maven central to be annoying since they are pretty much >> useless as Maven artifacts. >> >> Indeed. >> >> The issue here is that deleting files from a closed staging area is >> prone to errors as the Nexus GUI is quite fiddly (and the confirmation >> pop-up does not show the name of the file being deleted). >> >> > >> >> >> >>> I gave up trying to remove the absurd .asc.sha1 and >> >>> .asc.md5 files for JCI, there was too many of them (12 files per >> >>> artifact, 6 artifacts). >> >> >> >> That could be automated (I started working on a tool to do this, but >> >> other things intervened). >> >> It's a long-standing Maven bug. The files can be left, but it makes >> >> checking the directory tedious. >> > >> > See http://wiki.apache.org/logging/Log4j2ReleaseGuide step 11c. I'm >> not sure why rm *.asc.md5 is a problem. Even if they are in separate >> directories the find command works pretty well. >> >> Find and rm do not work on Nexus, which is one place where the >> spurious files are annoying. >> Also it's easy to delete the wrong file in Nexus (so this should be >> done before closing the staging area - if it is done at all) >> >> > Ralph >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >> For additional commands, e-mail: dev-help@commons.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org