Hello,
I've tagged and updated the version identifier of JBoss on the branch, so
that it is possible to checkout the sources to package the distributions,
included last minute Scott Stark's changes.
Packagers, see the how to below for instructions on how to checkout the
2.2.0 JBoss release.
Simon
How to:
First of all be sure that your CVSROOT is set properly, should be
:ext:[EMAIL PROTECTED]:/cvsroot/jboss where 'developer' is
your sourceforge account.
Command-liners can use the -d option to specify the CVSROOT, such as "cvs
-d:ext:[EMAIL PROTECTED]:/cvsroot/jboss checkout jboss".
Be very sure that the -d option is between the 'cvs' and any other command
(in the case above 'checkout')
WinCVS users have to specify it from the menu: Admin/Preferences.
Then perform the following command:
Command line:
cvs export -rJBoss_2_2_0_Final jboss
WinCVS 1.2:
>From the menu: Create/Checkout module
Then enter 'jboss' in the editable combobox titled "Enter the module
name..." and choose a folder to checkout to.
Click on the "Checkout Options" tab.
Select the checkbox titled "By revision/tag/branch" and enter
'JBoss_2_2_0_Final' in the editable combobox.
Select the checkbox titled "Do not create the CVS directories (export)".
Click OK.
This command exports all the sources, i.e. it's a regular checkout but
*without* the CVS directories.
This command is (normally) used for packaging, since there is no interest in
CVS directories for releases. This implies also that from that cvs-export
you cannot work with CVS, ie commit changes, etc (you should use the regular
checkout to work with CVS).
Anyway with this command you can build JBoss, do tests, run it, etc: fully
functional.
So, use this command to cvs-export JBoss, build the distribution, package
it, and that's it.
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
