At 08:35 PM 5/10/00 -0700, you wrote:
>Question: Is there a walkthrough for setting up JDE with XEmacs in a
>packaged environment?
>
>I am a pretty good Java programmer who is working on a pretty complex Java
>app. We have been developing for a couple years with no real debugger (can
>anyone say System.out.println("Got Here");). I have a huge src tree all
>packaged in a similar fashion to the old Java libraries...
>com.sun.blah.blah. I am looking to be able to step through any of our
>source code and possibly the JFC source. Can anyone point me in the
>direction of a good walkthrough?
>
1. Forget XEmacs if you are developing on Windows or are not a very
experienced XEmacs user capable of coping with Emacs vs. XEmacs
compatibility issues.
2. Download and install the latest beta version of the JDE from the
JDE website, following the installation instructions on the website.
Be sure to read the release notes that come with the beta.
3. Set up JDEbug, the JDE's integrated JPDA-based debugger, following
the instructions in the JDE user's guide (select JDE->Help->JDE User's
Guide).
4. Create a JDE project file (prj.el) file in your app's root directory.
See the JDE user's guide for detailed information on creating and saving
project files. Be sure to give the project a unique name when saving the
prj file.
4. Set the variable jde-db-source-directories to point to the root of the JDK
source tree and the root of your source tree.
5. Set the variable jde-run-application-class to the fully qualified name of
your application's main class.
6. Set the JDE's debug compile option to specify inclusion of full debug info.
7. Save all your variable setting in your project file, using
JDE->Project->Project File Save.
8. Compile your application. Note that if you have a makefile for your app
you can
bind it to the JDE's build command. See the user's guide for more info.
Note
also that there is a JDE add-on that generates a makefile for your project
automatically. See JMaker in the Contributions page on the JDE website.
9. Set a breakpoint in your app's main class, using JDEbug's set breakpoint
command
(JDEbug->Set Breakpoint).
10. Select JDE->Debug App. The JDE will start your app in debug mode and
run it to
the first breakpoint.
At this point, you can start stepping through the app and into any JDK
methods that
it invokes.
- Paul
------------------------------------------------------------
TECH SUPPORT POLICY
I respond only to requests that contain a complete problem report. The
easiest way to ensure that your report is complete is to include the output
of the JDE->Help->Submit Problem Report command in your request.
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
JDE website: http://sunsite.auc.dk/jde/
JDE mailing list archive:
http://www.mail-archive.com/[email protected]/maillist.html
