From 1c9bd8bf5f850d59592985b87394a9881a79982f Mon Sep 17 00:00:00 2001 From: Luke Taylor Date: Thu, 20 Dec 2007 17:47:05 +0000 Subject: [PATCH] Updates to release description. --- releasebuild.sh | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/releasebuild.sh b/releasebuild.sh index abad4d08ee..cb8715f150 100644 --- a/releasebuild.sh +++ b/releasebuild.sh @@ -5,7 +5,7 @@ # Release Process. # # 1. Do clean check out of source from svn and note revision number. -# 2. Switch to 1.4 JVM and run 'mvn test' from core directory. +# 2. TODO: JDK - 1.4 compatibility checks. # 3. Set the version number in the pom.xml files of all the modules. # 3a. If doing a release rather than snapshot build, run "find . -name pom.xml | xargs grep SNAPSHOT" and make sure # there are no important snapshot dependencies. @@ -13,6 +13,7 @@ # 4. Set the correct spring version number in the pom.xml. # 4a. Make sure there are no snapshot dependencies in the release. # 4b. Remove any references to external maven repositories in the parent pom.xml (remove element). +# 4c. Check that all dependencies are downloadable from maven central repo. # 5. Run this script to generate the artifacts and web site in the 'release' directory. # 6. Copy the archives and unpack them to check the contents. # 7. The archives are tar archives. Create zip versions from the contents and check the internal paths are Ok. @@ -21,13 +22,15 @@ # 10. Deploy the contacts and tutorial sample apps in Jetty and Tomcat and check they work. # 11. Check there have been no further commits since checkout (svn update). If there have, go to 1. # 12. Commit the source with the changed version numbers and note the revision number (should be 'build revision' + 1). -# 13. Update the pom file versions to the appropriate snapshot version, do a grep to make sure none have been missed +# 13. Label/tag the source tree with the release version number. +# 14. Update the pom file versions to the appropriate snapshot version, do a grep to make sure none have been missed # and commit them. -# 14. Upload the site to acegisecurity.org (or wherever). -# 15. scp the release archives to shell.sf.net. Check md5 matches to make sure transfer was OK. -# 16. ftp them to the sourceforge upload server, uploads.sourceforge.net. -# +# 15. Upload the site to acegisecurity.org (or wherever). +# 16. scp the release archives to shell.sf.net. Check md5 matches to make sure transfer was OK. +# 17. ftp them to the sourceforge upload server, uploads.sourceforge.net. +# 18. Put the jars, poms and signature files into the acegi repository for synchronization. # +# (alternatively, the maven release plugin takes care of a lot of this stuff). ######################################################################################################################## # @@ -149,7 +152,8 @@ NUM_JARS=`ls *.jar *.war | wc -l` if [ "$NUM_JARS" -ne 9 ] then - echo "Expected 9 Jar files but found $NUM_JARS." + echo "Expected 9 Jar files but found $NUM_JARS:" + ls *.jar *.war exit 1 fi