I updated the cvs admin doc to describe the steps for making a
change in a non-jboss module and incorporating the module jars
into the jboss release branch. I went through them for the jbosscx
changes and this is what was done:
Make a 2.4 branch for the jbosscx module:
1. cvs co jbosscx
2. cd jbosscx
3. cvs tag Rel_2_5_0_0
4. cvs tag -b Branch_2_4
5. cvs update -r Branch_2_4
6. cvs tag Rel_2_4_0_0
7. Make the required changes. All code changes had been made but the
version portion of the jbosscx.jar needed to be removed so I did that.
8. Commit the changes
9. Tag the jbosscx 2.4 branch with the next beta release tag in the jboss
module(not the jbosscx module). This happens to be Rel_2_4_0_1. From
within the root jbosscx working directory:
cvs tag Rel_2_4_0_1
10. Built the jbosscx.jar
11. Copied the jbosscx.jar into the jboss/src/lib directory
12. Removed the old jbosscx-0.2.jar
13. Added the new jbosscx.jar
14. Committed the changes
15. Tag the jboss module with Rel_2_4_0_1. From
within the root jboss working directory:
cvs tag Rel_2_4_0_1
16. Merge the change to build.xml made on the 2.4 branch to main. From
within a working directory created by cvs co jbosscx:
bash-2.04$ cvs update -j Rel_2_4_0_1
cvs server: Updating .
RCS file: /cvsroot/jboss/jbosscx/src/build/build.xml,v
retrieving revision 1.4
retrieving revision 1.4.2.1
Merging differences between 1.4 and 1.4.2.1 into build.xml
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
