At 09:03 AM 7/20/99 -0700, Karr, David wrote:
>I'd like to see if I can use JDE as JUST a standalone debugger. I already
>have good colorization and syntax editing for Java, I just need a good
>debugger. From what I can see, JDE tries to be much more than I need.
>
>>From a debugging point of view, it seems like I need to select a "project",
>which has various attributes, like:
>
>1. run directory
>2. classpath
>3. main class
>4. other "java" command-line arguments
>5. run class command-line arguments
>
>>From what I can see, JDE makes me reconfigure all of these things if I need
>to work on a different "project".
>
That is true, but you can save the settings in a "project" file, using the
JDE->Project->Save Project option. The settings are automatically restored
when you open a source file that belongs to the project. The JDE assumes
that the source files for a project reside in a separate directory tree.
When you save a project, the JDE saves the project file in the directory
containing the source file in the current buffer. The next time you open a
file anywhere in the directory tree whose root is the directory containing
the project file, the JDE loads the project file and executes its contents
thereby restoring all the saved settings. Similarly, if you switch from a
project A buffer to a project B buffer, the JDE automatically reloads the
project file. Thus, you can have multiple project files open. All this is
explained in great detail in the JDE User's Guide which you can view simply
by selecting Help from the JDE menu.
- Paul
