I've just removed the hard coded altDeploymentRepository as it was just for testing.
Right now if you do mvn -Prelease it will try to use Nexus as thats the default config and that will fail as we don't yet have access till the INFRA JIRA for that is done, so you need to specify the deployment repo, eg: mvn -Prelease -DaltDeploymentRepository=apache.rsync::default::scp://people.apache.org/home/antelder/public_html/test/maven or for testing you can use a local file system one mvn -Prelease -DaltDeploymentRepository=id::default::file:target/deploy which will create a top level target/deploy folder containing the repo. +1 on keeping the doc page in sync, and once we have this working well I'd like to go through and simplify the doc as much as possible. ...ant On Mon, Jun 14, 2010 at 3:20 PM, kelvin goodson <[email protected]> wrote: > I'm all for anything to help with reducing the pain of releasing. I > have been keeping the 2.x Making Releases doc up to date recently. It > would be a shame for it to go out of date so quickly, so I'd like to > make sure you or I update it to reflect this change. All the > branch/tag creation and rat report stuff etc will lneed to remain in > the doc. From a quick glance at the commit report for the updated pom > I couldn't see how I could safely try the release profile in a > sandboxed environment -- for example I'm not sure what maven magic > gets applied to turn ... > + > <altDeploymentRepository>id::default::file:target/deploy</altDeploymentRepository > into for example my staging repo on p.a.o > > can you jot down a few notes on how to use it please? > > Kelvin. > > On Mon, Jun 14, 2010 at 3:05 PM, ant elder <[email protected]> wrote: >> I've been updating the release profile in the build to try to make it >> easier to do releases. What we want is minimal commands to get all the >> artifacts signed and deployed but the release process currently has >> quite a lot of manual steps. The release profile now tries to automate >> all those steps, so you can just do mvn -Prelease and all the maven >> artifacts and distributions will get built, signed, and uploaded to >> the staging repository. There still a bit of clean up needed and >> presently the distributions are getting included in the staging repo >> so there is a manual step afterwards where you need to separate them >> out of that (does anyone have any ideas how to avoid this?), but >> already it should make it significantly easier to cut a release. >> >> ...ant >> >
