Perhaps your problem is related to this?
If you want to test your environment, try
downloading from cvs, build jboss and
run the testsuite.
Tried to build jboss from source.
Checked out the cvs module "jboss-all" at about 3/25/2003 8 p.m.
1. build.properties last line, should be "xdoclet/xdoclet" instead of xdoclet-xdoclet
2. common-logging.jar and common-collections.jar were not found. Linked them from thirdparty/.. to tools/lib
3. URLFilter is an inner interface of URLLister. Therefore URLListerBase has to qualify the reference to the interface. Compiliation failed.
At this point I gave up for today (16 hours).
Would be good to find out that all this is on my side. Not to loose the belief in quality of Java software. (It does not make sense to exchange VB by something that's not better)
Any other idea to get jboss running on debian a bit faster?
cvs ... co -r Branch_3_0 jboss-3.0
or replace Branch_3_0 with JBoss_3_0_6
Has anybody built Jboss from source recently?
It is being built from the source several times every day. Use the branch tag as Adrian pointed out
The entry from Adrian and mine of 29-03-2003 overlapped. Sorry.
With -r JBoss_3_0_6 I could build and start jBoss without errors. (There are still errors when I shutdown jBoss but I haven't analysed them yet)
Is such (Adrian-)information documented? Where? What else?
Minor concern: Why was the sourceforge information "check out module jboss-all" not ok for my case? I would recommend to think of the hundrets of people wasting their time as I did.
The CVS checkout structure was changed some time ago and there might still be documentation around with the old information.
This one looks like it has an up to date procedure for checking out different versions of JBoss:
This one has info on how specific release tags are named in case you don't want just the head of the branch: