Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification.
The "ReleaseDeployment" page has been changed by sebbapache: https://wiki.apache.org/commons/ReleaseDeployment?action=diff&rev1=4&rev2=5 Assuming ths can be automated, it would eliminate most of the error-prone stages. The Nexus staging area would still need to be closed (or maybe that can be automated?) but there would be no need to tidy up Nexus. + Experiments show that the scm-publish:publish-scm goal can be used to upload arbitrary folders to the SVN dist/dev tree + + And in theory there is a Nexus Maven plugin that can deploy a previously created staging tree. + + So the process would be: + * mvn deploy -Ptest-deploy + * use some script to move the tarballs into their own directory structure + * use scm-publish:publish-scm to publish the tarballs + * use Nexus Maven plugin to deploy & close the jars + + The script to move the tarballs could probably be written in Ant and invoked by Maven, e.g. using a specific profile. + + == Alternative tarball process == An alternative approach would be to detach the tarballs from the build. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
