This page covers how to use the new jboss build for JBossRemoting.  The traditional build is still available via the build.xml file, but will be replaced by this new build in the near future.

If going to use an IDE (like Intellij or Eclipse), perform all of these steps before creating your jboss remoting project within the IDE.  It is suggested to create a new directory, JBossRemoting for example, and change to that directory before executing following steps.

1. Check out the remoting project from cvs using 'cvs co -d remoting JBossRemoting'.  This will create a new 'remoting' directory in your root project directory.  This directory contains the JBossRemoting project source files. 

2. Check out the tools project from cvs using 'cvs co tools'.  This will create a new 'tools' directory in your root project directory.  This directory contains the libraries needed for the jboss build.

3. Create a cvs.properties file under root remoting directory.  Add entry for cvsroot indicating your cvs root.  For example:

cvsroot=cvsroot=:ext:joe@cvs.forge.jboss.com:/cvsroot/jboss

where 'joe' is your user name.  As it stands now, you will have to have a user id for accessing cvs, as the public anonymous pserver access will not work via the automated build.  This also means that you will need ssh-agent setup to run cvs without entering a password.  If you can execute steps 1 and 2 via a console without having to enter a password, you are good to go (otherwise will need to get a user id for cvs, which includes posting your public key, and making your private key available to your CVS_RSH). 

4. Go to the remoting directory and run 'ant -f release.xml synchronize'  This should pull down all the components needed for build and will create a 'thirdparty' dirctory in your root project directory.

5. Then run 'ant -f release.xml build'.  This will run the build for jboss remoting

The new build requires a standard structure for the project directories.  For JBossRemoting, this meant having to change the structure to comply, so will notice that the JBossRemoting project substructure now complies as follows:

remoting/src/etc

remoting/src/main

remoting/src/tests

Another change was to the actual packaging of the test classes.  The standard is to start with org.jboss.test..  Therefore, the remoting tests all fall under the org.jboss.test.remoting package structure.

6. Run tests

ant clean most tests.quick