Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 97148 invoked from network); 7 Dec 2007 23:33:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Dec 2007 23:33:11 -0000 Received: (qmail 63179 invoked by uid 500); 7 Dec 2007 23:32:59 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 63118 invoked by uid 500); 7 Dec 2007 23:32:58 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 63109 invoked by uid 99); 7 Dec 2007 23:32:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Dec 2007 15:32:58 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [82.209.166.4] (HELO smtp.bredband2.net) (82.209.166.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Dec 2007 23:32:37 +0000 Received: (qmail 30476 invoked from network); 7 Dec 2007 22:45:58 -0000 Received: from me-68-111-233-83.3.cust.bredband2.com (HELO [192.168.0.3]) ([83.233.111.68]) (envelope-sender ) by smtp.bredband2.net (qmail-ldap-1.03) with SMTP for ; 7 Dec 2007 22:45:58 -0000 Message-ID: <4759D815.3020100@apache.org> Date: Sat, 08 Dec 2007 00:32:37 +0100 From: Dennis Lundberg User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Jakarta Commons Developers List Subject: Re: [all] m2 release process References: <55afdc850712071058pef7e8d7tec6f5f4a7467b37@mail.gmail.com> <4759B4AD.2020701@apache.org> <55afdc850712071315h7ca3a1f0kccf0ecf1cdb67448@mail.gmail.com> In-Reply-To: <55afdc850712071315h7ca3a1f0kccf0ecf1cdb67448@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Niall Pemberton wrote: > On Dec 7, 2007 9:01 PM, Dennis Lundberg wrote: >> For logging I followed the current release procedure [1], which worked >> well. Sections 11 and 12 need to be merged somehow. As I'm not familiar >> with releases back in the Jakarta days, I'm not quite sure how to >> though. Other than that, it was obvious what to when the docs talk about >> Maven 1 specifics. But that's probably just me, because I'm used to >> doing releases with Maven 2 over in maven land. So this needs to be >> written down. >> >> For releases support artifacts that reside only in the Central repo >> (parent poms, skin) I have simply done: >> - vote based on svn revisions >> - mvn release:prepare >> - mvn -Prelease release:perform > > OK I found this http://tinyurl.com/2h222s and was following that. "mvn > release:prepare -Prc" works fine but the first time i did "mvn > release:perform -Prc" (fogetting -Darguments="-Prc") and I couldn't > find where it went and from the logs it looked like it uploaded it to > "dummy" - so I undid the prepare and tried again with: > > mvn release:perform -Prc -Darguments="-Prc" > > This time it threw a NullPointerException in the SurefirePlugin(line 594) > > So can I do "mvn -Prelease release:perform" without having to revert > the version 2 tag? If so how? We seriously need to remove the "dummy" repo setting from the parent pom. It does nothing but cause grief. If we remove it, calling 'mvn release:perform will copy the artifacts to the snapshot repo if the version is a SNAPSHOT, and to the central-sync-repo if it's a "real" version. We have to trust ourselves to call the right commands, not having to remember which non-standard command-line switch to add. Just use Maven the way it is. > > Niall > >> I'd be happy to help write some more docs for this. We can borrow some >> parts from Maven's own release processes, the old [2] and the new [3]. >> How do we want to structure the docs? >> >> 1. One document that includes all releases, whether it's Ant, Maven 1 or >> Maven 2 >> 2. Separate documents depending on which tool is used to do the release >> 3. Something else... >> >> >> [1] http://commons.apache.org/releases/release.html >> [2] http://maven.apache.org/developers/release/pmc-release-process.html >> [3] http://maven.apache.org/developers/release/releasing.html >> >> >> Niall Pemberton wrote: >>> I haven't done an m2 release before - do we have it documented >>> anywhere or can someone give me some pointers on what commands and >>> options I need to use? >>> >>> tia >>> >>> Niall >>> >>> P.S. This is for commons-skin >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >>> For additional commands, e-mail: dev-help@commons.apache.org >>> >>> >> >> -- >> Dennis Lundberg >> >> >> --------------------------------------------------------------------- >> 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 > > -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org