Suraj Acharya writes: > JDE also looks for tools.jar to check if a directory is a JDK > directory or not. Try creating > an empty tools.jar in the lib directory of your JDK. You will be able > to use the compile server, but it might let you used JDE with other > jdks.
The JDEE currently assumes that you are using Sun's toolset. I will look into supporting other tool sets as time permits. Paul > > Suraj > > > On Mon, 22 Nov 2004 23:25:05 -0500, Matt Kurjanowicz > <[EMAIL PROTECTED]> wrote: > > The tools.jar is the file that contains the compiler. This way JDEE can > > run > > the compiler directly using the classpath that JDEE sets. > > -Matt > > > > > > > > On Monday 22 November 2004 03:15 pm, Shyamal Prasad wrote: > > > Hi, > > > > > > I'm having trouble running JDEE (with both Emacs and XEmacs) on a > > > Debian GNU/Linux system. The problem is with finding the tools.jar > > > file. Since I'm using runtimes not licensed from Sun (sablevm, kaffe > > > etc.) this file is missing. > > > > > > Could some one explain to me (just a hint) why tools.jar is so > > > important to JDEE? I can run beanshell without it, and I'm not sure > > > what else might be needing it. > > > > > > Best regards, > > > Shyamal > > > > > > PS: I read this list via the web, so I would never complain about a Cc > > > :-) > > > > -- > > Matthew Kurjanowicz > > [EMAIL PROTECTED] > > CS 2110 TA > > College of Computing > > GEORGIA Institute > > of TECHnology > >
