Thanks Paul and Steve for putting together this information on how to install
and configure JDEbug. I finally got it working ofr one of my applications
(unfortunately not for a second one, and the configuration seems to be
identical. Oh my...).
A crucial piece of information that I was missing was that the jpda bin
directory need to be added not only to the system path, but to the Emacs load
path as well. Thanks, Paul!
A suggestion: since the JPDA installation seems to be such a source of problems,
with so many small things that can go wrong for the unitiated (like myself :)
why not put together a small diagnostic program, just something that the user
could run locally and would check for the appropriat environment variables and
Emacs settings, and provide more direct to the point error messages than the
ones from JPDA/JDI/JDWP... ? Such a tool could save quite some time in support.
Regards,
Nascif
Paul Kinnucan wrote:
> At 12:11 PM 4/17/00 -0500, you wrote:
> >Quick start for JDE with JDEbug, or how to get a single file compiling and
> >debugging in JDE.
> >
> >1. Download JDE and install in your ~/emacs/site directory (or wherever
> >you put your site-specific code).
> >
> >2. Download and install a JDK and the JDPA stuff from Sun's site.
> >
> >3. Now we'll set up the environment. Create your working directory (we'll
> >call it /user/work) and open or create a .java source file in that
> >directory. Set the following properties for this session only:
> >
> >Editing General settings (JDE -> Project -> Options -> General) (note that
> >this is called General in some places and Project in others):
> >
> >3.1. Turn on JDEbug.
> >
> >3.2. Edit JDE_Run_Java_Vm_W to put in full path. If you are on win32,
> >change javaw to java here.
> >
>
> Doing this causes a DOS command window to appear whenever you start the
> debugger. My recommendation is to leave jde-run-java-vm-w alone. The
> default value was chosen for a reason.
>
> Further, I recommend including the JDK bin directory in your system's path.
> That way, you never have to edit the default values for the vm and javac.
>
> >3.3. Edit JDE_Run_Java_Vm to put in full path
> >
> >The last two are not strictly necessary but on my machine I have several
> >jdks around and prefer to use fully qualified file names rather than rely
> >on the path.
> >
>
> I have found this to be very problematic, at least on Windows. The JDK
> installer updates the Windows registry. Thus, the registry always reflects
> the last JDK installed so that if you run another version, you are liable
> to get wrong settings.
>
> >3.4. Edit JDE_Global_Classpath to add my working directory (/user/work)
> >
> >3.5. Edit JDE_DB_Source_Directories to add working directory (/user/work)
> >
>
> I would recommend adding the JDK source directory so that the debugger will
> know where to go when you step into a Java API class. Note that one
> additional entry, e.g.,
>
> c:/jdk1.2.2/src
>
> is enough to account for the entire Java API source.
>
> Please note that you will find more detailed information on setting up
> JDEbug in the JDE user's guide (JDE->Help->JDE User's Guide).
>
> - 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
