Return-Path: X-Original-To: apmail-aries-dev-archive@www.apache.org Delivered-To: apmail-aries-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 A7E59FA97 for ; Thu, 28 Mar 2013 13:30:22 +0000 (UTC) Received: (qmail 59988 invoked by uid 500); 28 Mar 2013 13:30:21 -0000 Delivered-To: apmail-aries-dev-archive@aries.apache.org Received: (qmail 59815 invoked by uid 500); 28 Mar 2013 13:30:21 -0000 Mailing-List: contact dev-help@aries.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aries.apache.org Delivered-To: mailing list dev@aries.apache.org Received: (qmail 59774 invoked by uid 99); 28 Mar 2013 13:30:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Mar 2013 13:30:19 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jwross@us.ibm.com designates 32.97.182.137 as permitted sender) Received: from [32.97.182.137] (HELO e7.ny.us.ibm.com) (32.97.182.137) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Mar 2013 13:30:09 +0000 Received: from /spool/local by e7.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 28 Mar 2013 09:29:48 -0400 Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e7.ny.us.ibm.com (192.168.1.107) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Thu, 28 Mar 2013 09:29:46 -0400 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id C8AFDC9004A for ; Thu, 28 Mar 2013 09:29:45 -0400 (EDT) Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r2SDTioK344612 for ; Thu, 28 Mar 2013 09:29:45 -0400 Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r2SDTfpS000438 for ; Thu, 28 Mar 2013 07:29:41 -0600 Received: from d03nm691.boulder.ibm.com (d03nm691.boulder.ibm.com [9.63.34.16]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r2SDTfoS000418 for ; Thu, 28 Mar 2013 07:29:41 -0600 In-Reply-To: References:

Subject: Re: Subsystems Release X-KeepSent: 3CB8D5B1:51E92156-87257B3C:00496BB1; type=4; name=$KeepSent To: dev@aries.apache.org X-Mailer: Lotus Notes Release 8.5.3 September 15, 2011 Message-ID: From: John W Ross Date: Thu, 28 Mar 2013 08:29:35 -0500 X-MIMETrack: Serialize by Router on D03NM691/03/M/IBM(Release 8.5.3FP2 ZX853FP2HF5|February, 2013) at 03/28/2013 07:29:37 AM MIME-Version: 1.0 Content-type: multipart/alternative; Boundary="0__=08BBF1AFDFDAED218f9e8a93df938690918c08BBF1AFDFDAED21" Content-Disposition: inline X-TM-AS-MML: No X-Content-Scanned: Fidelis XPS MAILER x-cbid: 13032813-5806-0000-0000-00002082E554 X-Virus-Checked: Checked by ClamAV on apache.org --0__=08BBF1AFDFDAED218f9e8a93df938690918c08BBF1AFDFDAED21 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: quoted-printable The only thing that made this work for me was creating a profile in my settings.xml, adding forked-path as = a property, then specifying that profile as part of the release:prepare a= nd release:perform commands. None of the other listed solutions worked (i.= e. specifying forked-path as a property= of the maven-release-plugin configuration, specifying -Dgpg.passphrase=3D"xxxxxxx" -Darguments=3D"-Dgpg.passphrase=3Dxxxxxxxx= x" as command line arguments, or specifying -Dgpg.userAgent=3Dtrue as a comma= nd line argument). John > > Re: Subsystems Release > > I don't remember how I used to get this to work :-( > > I would ask on the maven-users list (or search it first) or on maven = irc. > > good luck :-) > david jencks > > On Mar 26, 2013, at 12:02 PM, John W Ross wrote: > > > > > > > When preparing the release of the subsystem.api bundle, the process= hangs > > during the signing phase. > > > > [INFO] [INFO] --- maven-gpg-plugin:1.0-alpha-4:sign (default) @ > > org.apache.aries.subsystem.api --- > > > > I let it hang for more than an hour before finally killing it. I suspect > > this is because I am unable to copy > > https://svn.apache.org/repos/asf/aries/KEYS (which contains my publ= ic key) > > to http://www.apache.org/dist/aries/KEYS due to insufficient privileges. I > > am able to get the updated KEYS file to my home directory on > > people.apache.org but can't copy or move it > > to /www/www.apache.org/dist/aries/KEYS. > > > > How do I receive the necessary permissions for this? > > > > John > > > >> > >> Re: Subsystems Release > >> > >> Thanks, David. I had not followed those instructions. I now have a= nd am > >> able to deploy snapshot releases. > >> > >> John > >> > >>> > >>> Re: Subsystems Release > >>> > >>> Did you follow the instructions on setting up your settings.xml f= ound > >> here? > >>> > >>> http://www.apache.org/dev/publishing-maven-artifacts.html > >>> > >>> hope this might help :-) > >>> david jencks > >>> > >>> > >>> > >>> On Mar 22, 2013, at 8:21 PM, John W Ross wrot= e: > >>> > >>>> > >>>> > >>>> I received the following error while attempting to create a snap= shot > >>>> release per the instructions at > >>>> http://aries.apache.org/development/releasingaries.html. > >>>> > >>>> [ERROR] Failed to execute goal > >>>> org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy > >> (default-deploy) on > >>>> project org.apache.aries.subsystem.api: Failed to deploy artifac= ts: > >> Could > >>>> not transfer artifact > >>>> org.apache.aries.subsystem:org.apache.aries.subsystem.api:jar:1.= 0. > >>> 0-20130323.025945-55 > >>>> from/to apache.snapshots.https > >>>> (https://repository.apache.org/content/repositories/snapshots): > > Failed > >> to > >>>> transfer file: > >>>> https://repository.apache.org/content/repositories/snapshots/org= / > >>> apache/aries/subsystem/org.apache.aries.subsystem.api/1.0.0- > >>> SNAPSHOT/org.apache.aries.subsystem.api-1.0.0-20130323.025945-55.= jar. > >>>> Return code is: 401, ReasonPhrase:Unauthorized. -> [Help 1] > >>>> > >>>> So I'm going to halt my attempt at a subsystems release until assured > >> that > >>>> I have the necessary permissions or am corrected in my approach.= > >>>> > >>>> John > >>>> > >>>>> > >>>>> Re: Fw: Subsystems Release > >>>>> > >>>>> > >>>>> How do I ensure that https://svn.apache.org/repos/asf/aries/KEY= S has > >> been > >>>>> mirrored to @people.apache.org:/www/www.apache.org/dist/aries/K= EYS? > >>>>> > >>>>> I tried using scp but received the following: > >>>>> > >>>>> scp: /www/www.apache.org/dist/aries/KEYS: Permission denied > >>>>> > >>>>> John > >>>>> > >>>>>> > >>>>>> Re: Fw: Subsystems Release > >>>>>> > >>>>>> Agree with David. > >>>>>> > >>>>>> The bundle versioning plugin only comes into play after you ha= ve > >>>> released > >>>>>> the base. > >>>>>> Thanks > >>>>>> Emily > >>>>>> > >>>>>> On Wed, Mar 20, 2013 at 1:40 PM, David Bosschaert < > >>>>>> david.bosschaert@gmail.com> wrote: > >>>>>> > >>>>>>> Hi John, > >>>>>>> > >>>>>>> On 20 March 2013 12:22, John W Ross wrote= : > >>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> I have a few questions regarding the Aries release process (= > >>>>>>>> http://aries.apache.org/development/releasingaries.html). > >>>>>>>> > >>>>>>>> (1) I presume we've already had the required discussion of t= he > >>>>> release > >>>>>>> and > >>>>>>>> its contents? Does anyone object to the initial 1.0.0 releas= e of > >>>>>>>> Subsystems? The contents of the release would be everything = in > >>>> trunk. > >>>>>>>> > >>>>>>> > >>>>>>> It's been flagged a few times already on this list. I think a= s far > >>>> back > >>>>> as > >>>>>>> October or November last year. I didn't see any objections an= d > >>>> there's > >>>>>>> certainly no objection from me... > >>>>>>> > >>>>>>> > >>>>>>>> (2) The instructions state "Make sure that there is a JIRA > > version > >>>>> that > >>>>>>>> matches the name of the release, if not, create one." I don'= t > >>>>> understand > >>>>>>>> what this means. > >>>>>>>> > >>>>>>> > >>>>>>> I guess that this is to make sure that people can file bugs > > against > >>>> it. > >>>>>>> While there isn't a "subsystems-1.0" jira version, there is a= > > simple > >>>>> "1.0". > >>>>>>> I don't know but to me it looks like that would be enough > > otherwise > >>>> if > >>>>>>> you'd have specific versions for every component the number o= f > >>>> versions > >>>>> in > >>>>>>> JIRA would explode pretty soon... > >>>>>>> > >>>>>>> > >>>>>>>> (3) Where does the maven-versioning plugin come into play? H= ow do > > I > >>>>>>> insure > >>>>>>>> the subsystems project is correctly configured to use it? > >>>>>>>> > >>>>>>> > >>>>>>> I thought that this would come into play *after* the first > > release, > >>>> so > >>>>> it > >>>>>>> would not be applicable this time if I'm not mistaken... > >>>>>>> > >>>>>>> Just my 2c, > >>>>>>> > >>>>>>> David > >>>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> Thanks > >>>>>> Emily > >>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >>>>>> Emily Jiang > >>>>>> ejiang@apache.org >= --0__=08BBF1AFDFDAED218f9e8a93df938690918c08BBF1AFDFDAED21--