open a shell...
I did that...didn't work.
I must have screwed up when I checked out.
Instead of module jboss-all I checked out '.'
So, I'm gonna try the checkout portion again.
I'll tell 'ya how it goes.
Ok, that worked...thanks Al.
To restate the error of my ways....
Wrong: Checkout the '.' module and try to build.
Right: Checkout the jboss-all module and try to build.
Also be advised that I found a bug in the jetty integration. It doesnt seem to propogate the security if you protect areas of your web site. I fixed it by copying 3 jar files from my jboss-2.4.3-jetty-3.1.1 installation to the lib/ext directory of jboss 3. (org.mortbay.jetty.jar, org.apache.jasper.jar, and javax.servlet.jar) I didnt try to track it exactly since copying these three solved my problem and i could get on with the development of the app im working on. I know Jules is looking at Jboss-3's jetty this weekend so i sent him an email about it, but if you are using protected web areas this will at least get you running till then.
When I tried to build the fella recently, I found that I needed the buildmagic classes. I got:
[taskdef] Could not load definitions from resource planet57/tools/buildmagic/t
ask/autoload.properties. It could not be found.
C:\cvs\jboss-all\server\build.xml:23: taskdef class planet57.tools.buildmagic.ta
sk.Property cannot be found
When I checked out sourceforge for the classes, I found that they are not available yet.
Have you guys managed to find them anywhere?
What I was doing wrong, was
That sorted out most of the worries.