On Mon, 2004-11-22 at 15:15, Shyamal Prasad wrote:
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.
I don't know
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
Paul == Paul Kinnucan [EMAIL PROTECTED] writes:
Paul It also allows users who are, like myself, working in a
Paul multilanguage environment (e.g., C/C++/Java) to use a single
Paul environment for all their work.
This is my primary motivation for using emacs, and JDE for java. I use
many
Ralph Jorre writes:
I don't often use a debugger but I have found JSwat very good and I just
wonder if it wouldn't be more efficient to just include some hooks so as
to be able to incorporate it efficiently.
Maybe this would be easier to maintain than rewriting the debug.
I plan
I had thought of this as well. Perhaps the JSwat maintainer would be
interested in working on it. If you download the JSwat CVS code, you
see they arleady use JDEE. See:
http://home.nc.rr.com/nascifandelaine/jswat.el
Paul Kinnucan [EMAIL PROTECTED] writes:
Ralph Jorre writes:
I don't
On Fri, 21 Feb 2003, [EMAIL PROTECTED] wrote:
It is hopeless for the JDEE to try to compete
feature-for-feature with dedicated Java IDE's, especially
commercial IDE's.
Maybe to further this, create an email list called, jde-plugin,
or something like it. Then, as people want to discuss this
Galen Boyer writes:
On Fri, 21 Feb 2003, [EMAIL PROTECTED] wrote:
It is hopeless for the JDEE to try to compete
feature-for-feature with dedicated Java IDE's, especially
commercial IDE's.
Maybe to further this, create an email list called, jde-plugin,
or something like it.
Paul,
For what it's worth, I absolutely agree with you on the need for debugging
support. I still follow the JDEE mailing list but I had to drop JDEE for
Eclipse almost a year ago because of the lack of debugging support ... I can
live with it on a small project, but on a large project (esp.
I agree, although I personally don't really care for #4. I would add that
displaying variables on a large object tree may be extremely slow if data are
being sent between emacs and java.
Milan
On February 21, 2003 03:41 pm, Chitale, Sandip V wrote:
I agree with you.
In terms of features in
I agree with you.
In terms of features in debugger I would like to see -
1. fast update to different views
2. better variables view (I would like to suggest Java based GUI for
this i.e. a treetable)
3. storing and managing breakpoints
4. breakpoint grouping
4. Different kinds of breakpoints
I could not agree more. We love JDEE because we love emacs. Emacs
will always be a better editor than any other IDE, therefore JDEE will
always be better for editing then any other IDE. Throw in the
compiling and debugging tools already there, and it's already an
excellent tool.
Hopefully
Chitale, Sandip V writes:
I agree with you.
In terms of features in debugger I would like to see -
1. fast update to different views
2. better variables view (I would like to suggest Java based GUI for
this i.e. a treetable)
This is planned.
3. storing and managing breakpoints
Hello Paul et al:
3. storing and managing breakpoints
This is my #1 wish list. Back in the JDE 2.1.5 days I had files full
of:
stop in corba.hcks.Client.testMisc
It was great. I never had to visit a file just to set a breakpoint.
Thanks,
Harold
Chitale, Sandip V writes:
I agree with you.
In terms of features in debugger I would like to see -
1. fast update to different views
2. better variables view (I would like to suggest Java
based GUI for this i.e. a treetable)
This is planned.
3. storing and
14 matches
Mail list logo
