Dear Wiki user, You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification.
The following page has been changed by WendySmoak: http://wiki.apache.org/struts/StrutsMavenRelease The comment on the change is: Some updates after the name change. ------------------------------------------------------------------------------ = Struts Maven 2 Release Process = - == 1. Releasing Struts Action 1 == + == 1. Releasing Struts 1 == - 1. Create the new directory on people.apache.org, for example people.apache.org/dist/struts/action/v1.3.x (no, don't actually use 'x') + 1. Create the new directory on people.apache.org, for example people.apache.org/dist/struts/v1.3.x (no, don't actually use 'x') - 1. Ensure that your settings.xml contains a <server> for apache-maven-test-builds (see the Suggested Settings section on StrutsMaintenanceMaven) + 1. Ensure that your settings.xml contains a <server> for apache.snapshots (see the Suggested Settings section on StrutsMaintenanceMaven) 1. Clear out your local Maven repo 1. Build and test all jar and war artifacts. Build and deploy the website. - 1. Build and deploy the jars and poms only. + 1. Build and deploy (jars and poms only) to the snapshot/test build repo. - 1. Create the assembly and upload it to cvs.apache.org/dist + 1. Create the assembly and upload it to people.apache.org/dist - 1. Make sure that everything under maven-snapshot-repository/org/apache/struts/ and www/struts.apache.org/struts-action is group writeable + 1. Make sure that everything under maven-snapshot-repository/org/apache/struts/ and www/struts.apache.org/struts1.x is group writeable - 1. Create and upload signatures for all .jar and .pom files in maven-snapshot-repository, and the .zip assembly file. + 1. Create and upload signatures for all .jar and .pom files in maven-snapshot-repository, and the .zip assembly files. {{{ - ~/svn/struts/STRUTS_ACTION_1_3_X + ~/svn/struts/STRUTS_1_3_X - $ rm -rf $M2_REPO/org/apache/struts/action + $ rm -rf $M2_REPO/org/apache/struts $ mvn install site site:deploy -P apps,itest $ mvn deploy -P pre-assembly $ cd assembly $ mvn assembly:assembly - $ scp target/assembly/out/* people.apache.org:/www/people.apache.org/dist/struts/action/v1.3.x + $ scp target/assembly/out/* people.apache.org:/www/people.apache.org/dist/struts/v1.3.x }}} == 2. Releasing the struts-parent pom == 1. Update the version number in maven/pom/pom.xml (remove -SNAPSHOT) and commit changes 1. Post release vote on dev@ - 1. 'mvn deploy' to deploy to dist/maven-repository + 1. 'mvn deploy' to deploy to maven-snapshot-repository 1. Upload a signature for the deployed pom + 1. Move the files to dist/maven-repository (? still need to work out details...) - 1. Request on [EMAIL PROTECTED] that dist/maven-repository/org/apache/struts be synched to ibiblio + 1. Request on [EMAIL PROTECTED] that dist/maven-repository/org/apache/struts be synced to ibiblio 1. Update the version number to the next SNAPSHOT and commit changes (Can this be done with release:prepare release:perform? Where would we put the tag that it wants to create?) - - == 3. Releasing the struts-build extension jar == - - [TODO] == 3. References ==
