I realize that this elementary material for most of you, but it does address some of the questions I have seen posted over the last week or so on these lists. In order to reach a wider audience I should probably repost this mailing to the forums, AOL, etc...
Ok, Branch_3_0 worked (sorry about the rant), which suggests the following algorithm for getting a recent build to work: 1. Don't bother with the packages posted on sourceforge or the JBoss site - these usually won't work. Instead, search the commits, i.e.,: [EMAIL PROTECTED] for a <branch-tag> that someone high-up - like Scott Stark - is committing to. It will appear as follows: > User: starksm > Date: 02/10/30 22:46:02 > > Modified: src/main/org/jboss/invocation/http/server Tag: Branch_3_0 > HttpInvokerHA.java Note the <branch-tag> Tag: Branch_3_0 2. Go to sourceforge.net/projects/jboss and browse the modules file: click on "Browse the CVS repository," then click CVSROOT, then the "modules" file. Use your browser's search dialog to do a find on "(view)" because it is hard to locate visually. 3. Now do a search on <branch-tag> (in this case "Branch_3_0"). 4. Scroll up to the # project definition (see below) under which <branch-tag> is defined. The module names are listed in the left-most column: E.g. jboss-all and jboss-3.0 (hint: pick jboss-3.0 - I haven't tested jboss-all - actually it might be better - I didn't notice it before for some reason, but they are defined identically anyway it now seems.) To recap: Branch_3_0 is the branch tag and jboss-3.0 is the module name that you will use in the cvs checkout command. 5. cd to the directory on your local machine immediately below which you would like the cvs server to create the jboss-3.0 directory. 6. type: CVSROOT=:pserver:[EMAIL PROTECTED]:/cvsroot/jboss Note that this will only affect the shell associated with the current terminal, so you don't have to worry about it screwing up other settings in other terminals that may be running on your machine. 7. Type cvs login and hit the space bar when prompted for a password. Or you can combine these two steps as follows: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/jboss login but setting CVSROOT will make your life easier. 8. Type cvs co -r Branch_3_0 jboss-3.0 or (on a single line) cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/jboss co -r Branch_3_0 jboss-3.0 The general form of the command for checking out a branch is: cvs co -r <branch-tag> <module-name> whereas a "trunk" module is simply: cvs co <module-name> Note: "co" is just an abbreviation for "checkout." So wherever "co" appears above, it can be replaced with "checkout," as in: cvs checkout -r Branch_3_0 jboss-3.0 9. Wait for the server to spew. The download should take a while to complete. In my case, the last package was the sax parser. If it stalls (for, like, 5 minutes or some incredibly long time), hit CNTL-C, cd to the <module-name> directory and type: cvs update You might want to do this even if it completes - but I recommend not updating unless you are sure that something is wrong. 10. Once you are sure you have everything, cd to the "build" subdirectory and type: ./build.sh 11. If it builds, celebrate. If it fails, make sure you are running a standard VM, preferably 1.4 - JBoss uses the first VM on your path and ignores JAVA_HOME. As for ant, I have conflicting information on this - the build scripts appear to ignore the local installation, but I read somewhere that you must have ant 1.5 - I have the latest 1.5 at this time. As a last resort, choose a different module (e.g., jboss-all instead of jboss-3.0). NOTE: Red Hat 8.0 will put a non-standard VM on your path that is not compatible with JBoss. This will cause the build to fail on an error relating to JJTree to the effect that OUTPUT_DIR is "not understood." 12. If and when you get it to build, cd to the "output/bin" subdirectory of the "build" subdirectory of <module-name> and type ./run.sh 13. Pray to your god. 14. If it runs, point your browser to: http://localhost:8080/jmx-console/ (I just tested it and it works with 8080) but they keep changing the port - so you might need to use a port scanner like nmapfe to locate the secret port. 15. Run the tests or pound away at the buttons on the console until it barfs an exception - then keep pounding - this is the fun part where you can get your aggressions out. When I ran 3.0.3 I got like 45 failures and it barfed a nasty exception on the second buttom I hit. I haven't played with this one yet. Have fun. Ben ## ## JBoss Project (3.0.x) also known as jboss-all ## ## NOTE: You still must specify the -r Branch_3_0 to get the correct ## version of this project. This only provides proper structure ## it can not specify the CVS tag. ## # Project definition jboss-all -d jboss-all \ build/jboss/etc/root \ &tools \ &_jboss_build \ &_jboss_j2ee \ &_jboss_common \ &_jboss_system \ &_jboss_naming \ &_jboss_server \ &_jboss_ejb \ &_jboss_pool \ &_jboss_connector \ &_jboss_messaging \ &_jboss_security \ &_jboss_cluster \ &_jboss_jmx \ &_jboss_varia \ &_jboss_testsuite \ &_jboss_jetty \ &_jboss_catalina \ &_jboss_catalina41 \ &_jboss_dotnet \ &_jboss_iiop \ &_jboss_management \ &_jboss_blocks \ &_jboss_transaction \ &_jboss_console \ &_jboss-3.0_thirdparty jboss-3.0 -d jboss-3.0 \ build/jboss/etc/root \ &tools \ &_jboss_build \ &_jboss_j2ee \ &_jboss_common \ &_jboss_system \ &_jboss_naming \ &_jboss_server \ &_jboss_ejb \ &_jboss_pool \ &_jboss_connector \ &_jboss_messaging \ &_jboss_security \ &_jboss_cluster \ &_jboss_jmx \ &_jboss_varia \ &_jboss_testsuite \ &_jboss_jetty \ &_jboss_catalina \ &_jboss_catalina41 \ &_jboss_dotnet \ &_jboss_iiop \ &_jboss_management \ &_jboss_blocks \ &_jboss_transaction \ &_jboss_console \ &_jboss-3.0_thirdparty ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
