Re: Ongoing bsh interface problem

Glenn Murray <[email protected]>
Newsgroups gmane.emacs.jdee
Message-ID <Pine.LNX.4.64.0603091939410.6191@localhost>
Hi Suraj,

Indeed it has been broken for some years, it seems my problem is
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=234416

However this doesn't explain the problem of the long search through my
home directory.  I put the official jde 2.3.5 jars mentioned below in
/usr/share/emacs21/site-lisp/java/lib/ (which is where the bsh
classpath looks for them).  I unset CLASSPATH by

~/$ export CLASSPATH=

When I open Emacs with Test.java in ~/testemacs/ (which contains only 
Test.java) and do C-c C-v C-c,  everything seems to be fine.

However when I open ~/Test.java it compiles OK, but I get an "Updating
class list for /home/glenn" message and it seems to be traversing my
entire home directory: *JDEE bsh* fills up swith "Cannot read contents
of /home/glenn/.wine/dosdevices/z:/usr/..." lines.  The buffer starts
with


cd /home/glenn/
/usr/lib/j2sdk1.5-sun/bin/java -classpath 
/usr/share/emacs21/site-lisp/java/lib/bsh.jar:/usr/share/emacs21/site-lisp/java/bsh-commands:/usr/share/emacs21/site-lisp/java/lib/checkstyle-all.jar:/usr/share/emacs21/site-lisp/java/lib/jakarta-regexp.jar:/usr/share/emacs21/site-lisp/java/lib/jde.jar:/usr/lib/j2sdk1.5-sun/lib/tools.jar 
bsh.Interpreter

BeanShell 2.0b2 - by Pat Niemeyer ([email protected])
bsh %


but the bsh process will eventually crash (if I don't do a kill
first).

Thanks for any help,
Glenn




On Thu, 9 Mar 2006, Suraj Acharya wrote:
> (I forgot to reply to the group earlier.)
>
> Glenn,
>
> The debian package is definitely broken. The java/lib directory in jde
> 2.3.5contains the following files:
>
> LICENSE.apache      RIGHTS.antlr        checkstyle-all.jar  junit.jar
>
> LICENSE.checkstyle  bsh.jar             jde.jar             sun_checks.xml
>
> Not having the checkstyle-all.jar in your path shouldn't hurt unless you try
> to run M-x jde-checkstyle.
>
> Suraj
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.