[jboss-cvs] JBossAS SVN: r58623 - trunk/build

[jboss-cvs-commits at lists.jboss.org]

Author: ryan.campbell at jboss.com
Date: 2006-11-18 15:04:03 -0500 (Sat, 18 Nov 2006)
New Revision: 58623

Modified:
   trunk/build/build-release.xml
Log:
release script updates for 5.0

Modified: trunk/build/build-release.xml
===================================================================
--- trunk/build/build-release.xml	2006-11-18 19:53:00 UTC (rev 58622)
+++ trunk/build/build-release.xml	2006-11-18 20:04:03 UTC (rev 58623)
@@ -3,18 +3,18 @@
 
 Structure: This script creates a self contained release structure rooted
 under a directory corresponding to the release version number. Under this
-are the cvs source tree and dist binaries. The structure for the jboss-4.0.1
+are the cvs source tree and dist binaries. The structure for the jboss-5.0.1
 release would be:
 
-4.0.1
-+ jboss-4.0 - the cvs source tree tagged with JBoss_4_0_1
+5.0.1
++ jboss-5.0 - the cvs source tree tagged with JBoss_5_0_1
 + dist - the release binaries
 
 Prequisites:
 1. The cvs branch to build the release for must have been tagged with the
-release tag, for example, JBoss_4_0_1, JBoss_4_0_1_RC1 etc:
+release tag, for example, JBoss_5_0_1_GA, JBoss_5_0_1_CR1 etc:
 
-[starksm at cvs releases]$ cvs rtag -r Branch_4_0 JBoss_4_0_1 jboss-4.0
+[starksm at cvs releases]$ svn cp https://svn.jboss.org/repos/jbossas/trunk  https://svn.jboss.org/repos/tags/JBoss_5_0_0_Beta1
 
 Steps:
 1a. Take the build/build-release.xml file from the branch cvs tree
@@ -22,9 +22,9 @@
 build. For example /usr/jboss/releases.
 
 1b. If you don't have the release cvs branch, you can co just the
-build-release.xml using a co like:
+build directory using a co like:
 
-cvs co -r Branch_4_0 _jboss_build/build-release.xml
+svn co https://svn.jboss.org/repos/tags/JBoss_5_0_0_Beta1/build
 
 Now you need to create a release.properties file containing the version
 properties to use for the release branch checkout. For example, the
@@ -69,7 +69,7 @@
    <!-- Include the environment properties -->
    <property environment="env"/>
    <!-- The cvs top level module name -->
-   <property name="cvs.module" value="jboss-4.0.x"/>
+   <property name="cvs.module" value="trunk"/>
    <!-- Set the cvs.tag based on the release.version.* properties -->
    <!-- Set the cvs.tag based on the release.version.* properties -->
    <condition property="cvs.tag" value="JBoss_${release.version.major}_${release.version.minor}_${release.version.revision}_${release.version.tag}">