I remember when I did it that I had checked out the tag from SVN and done the release:perform voodoo from there. I didn't get anywhere fast with -DconnectionUrl, but I couldn't tell you why not.
*kicking self for not documenting that at time, KNEW it was gonna come back to haunt me* On Dec 7, 2007 1:27 PM, Niall Pemberton <[EMAIL PROTECTED]> wrote: > On Dec 7, 2007 9:15 PM, Niall Pemberton <[EMAIL PROTECTED]> wrote: > > On Dec 7, 2007 9:01 PM, Dennis Lundberg <[EMAIL PROTECTED]> 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? > > OK I tried the following: > > mvn -Prelease release:perform > -DconnectionUrl=scm:svn: > https://svn.apache.org/repos/asf/commons/proper/commons-skin/tags/commons-skin-2 > > but I still can't see where its gone (doesn't seem to be in > m2-snapshot-repository or m2-ibiblio-rsync-repository) and logs seem > to indicate its being uploaded to "dummy" - any ideas? > > Niall > > > 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: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > -- > > > Dennis Lundberg > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
