A non list subscriber sent me a suggestion that fixed this
problem and a few other Beanshell problems.
When using XEmacs and a custom install of JDE, be sure to
delete the JDE subdir under etc in the XEmacs install dir.
This directory was on my system (and JDE was install elsewhere)
which caused the beanshell errors.
A quick check is:
Start the interpreter from the JDE menu and see what the classpath is in the
beanshell buffer.
Thanks for the help!
Brian Krisler
On Thursday 23 August 2001 04:13 pm, Brian Krisler wrote:
> I was just browsing the Java source code and I noticed the error below.
> I am not sure if this is from a read only file or a file that doesn't have
> a project associated with it.
>
> System
> JDE 2.2.8beta4
> XEmacs 21.2
> Linux
>
> (2) (error/warning) Error in `post-command-hook' (setting hook to nil):
> (error Beanshell eval error. See messages buffer for details.)
>
> Note: file is write protected
> Setting JDE variables to startup values...
> Beanshell expression evaluation error.
> Expression: jde.util.JdeUtilities.setProjectValues("nil", "");
> Error: // Error: bsh.EvalError: Error in method invocation: Method
> setProjectValues(java.lang.String, java.lang.String) not found in
> class'jde.util.JdeUtilities' : jde .util .JdeUtilities .setProjectValues (
> "nil" , "" )
>
> ArrayList.java:
> [##########################################################################
>####################] ... done
> Setting JDE variables to startup values...
> Beanshell expression evaluation error.
> Expression: jde.util.JdeUtilities.setProjectValues("", "");
> Error: // Error: bsh.EvalError: Error in method invocation: Method
> setProjectValues(java.lang.String, java.lang.String) not found in
> class'jde.util.JdeUtilities' : jde .util .JdeUtilities .setProjectValues (
> "" , "" )
