On Tue, 2010-06-08 at 21:20 +0100, sebb wrote: > I'd like to suggest the following updates to the HC parent POM: > > 1) add the following profile: > > <!-- > | Profile to allow testing of deploy phase > | e.g. > | mvn deploy -Ptest-deploy -Prelease -Dgpg.skip > --> > <profile> > <id>test-deploy</id> > <properties> > > <altDeploymentRepository>id::default::file:target/deploy</altDeploymentRepository> > </properties> > </profile> > > I found this very useful in BSF3 for checking the contents of Maven artifacts > > 2) Change the <distributionManagement> section URLs to be the same as > in the Apache parent POM v7. > > This would mean that Maven deployment would be done via Nexus, rather > than directly to the live forge. A lot safer, as the artifacts cannot > be accidentally released. > > It also allows the artifacts to be reviewed before release. > Also, Nexus performs checks on the sigs and hashes (e.g. I forgot to > publish my new key to the key server, and it would not let me upload). > > The RM would need to login to Nexus in order to close the upload, and > then use Nexus again once the vote has completed, but this does not > take long. > > Thoughts? >
+1 to both. Could you please, though, update the release process description to incorporate the steps necessary to stage release artifacts in Nexus and promote them to the official repository? http://wiki.apache.org/HttpComponents/HttpComponentsCoreReleaseProcess Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
