Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 21159 invoked from network); 20 Oct 2009 21:26:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Oct 2009 21:26:06 -0000 Received: (qmail 61978 invoked by uid 500); 20 Oct 2009 21:26:05 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 61856 invoked by uid 500); 20 Oct 2009 21:26:05 -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 61846 invoked by uid 99); 20 Oct 2009 21:26:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Oct 2009 21:26:05 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.221.183] (HELO mail-qy0-f183.google.com) (209.85.221.183) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Oct 2009 21:25:57 +0000 Received: by qyk13 with SMTP id 13so2504888qyk.27 for ; Tue, 20 Oct 2009 14:25:36 -0700 (PDT) MIME-Version: 1.0 Sender: jcarman@carmanconsulting.com Received: by 10.229.26.149 with SMTP id e21mr952264qcc.66.1256073936102; Tue, 20 Oct 2009 14:25:36 -0700 (PDT) In-Reply-To: <55afdc850910201421r79afaf5fj3bf5da178fa19f81@mail.gmail.com> References: <55afdc850910201118p7484dd4el623b53329dcbdac0@mail.gmail.com> <4ADE09BF.9050706@apache.org> <55afdc850910201421r79afaf5fj3bf5da178fa19f81@mail.gmail.com> From: James Carman Date: Tue, 20 Oct 2009 17:25:16 -0400 X-Google-Sender-Auth: 75f0407c1c112c8d Message-ID: Subject: Re: Problems releasing commons-parent 12 To: Commons Developers List Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Oct 20, 2009 at 5:21 PM, Niall Pemberton wrote: > I've tried it four times and it has failed with the same problem each > time. One of the changes in this release was to upgrade the > maven-release-plugin from version 2.0-beta-7 to 2.0-beta-9. Perhaps I > should try reverting that changes and see if that fixes it. Can't > think of anything else to try, unless someone else wants to have a go > and see if it works for them. I've had trouble with the release plugin lately, too. What I did to fix my problem was try the release, get the failure because of SVN issues, then do svn update, then retry the release. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org