Rick,
Thanks for the information. It looks like there isn't a need to use
JBuilder to do my JBoss compiles, since I would need two different JBuilder
projects, one to do the build and the other to run the server. And since
the Ant scripts for JBoss work so well, I can make my changes and compile
from the command line then debug from JBuilder without changing any
JBuilders settings.
Is this what you would recommend for building and debugging JBoss?
Thanks for your help,
Brett
----- Original Message -----
From: "Rick Horowitz" <[EMAIL PROTECTED]>
To: "jBoss" <[EMAIL PROTECTED]>
Sent: Wednesday, October 11, 2000 10:46 AM
Subject: Re: [jBoss-User] Running JBoss within JBuilder debugger
> If you're running JBuilder Foundation (which doesn't support remote
> debugging) here's how I've set it up. When I run jBoss, I only include
> jboss/bin/run.jar and jboss/conf in the JBuilder "required library".
> Make sure you specify the source for that required library to point to
> the jBoss sources. Then start jBoss in the debugger. During
> initialization, jBoss adds the rest of its jar files to the runtime
> classpath. Once this has completed, click on JBuilder's add to project
> button, and the rest of jBoss' packages will now be visible. Select the
> org.jboss package to add to the project. Once you do this, you will be
> able to debug into all of the jboss code.
>
> This is a bit of a pain, caused by jBoss dynamically determining its
> classpath from its lib and lib/ext directory contents, and from the
> ClassPathExtension entries in jboss.conf, but seems to be the price paid
> for this flexibility. If you discover a way around these extra steps,
> please post it.
>
> Hope this helps,
>
> Rick Horowitz
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
