At 06:45 PM 5/2/00 -0400, you wrote:
>That looks like an incredible useful functionality I really should be more
>advertised! But I'm having some trouble to get it to work. I was getting
error
>messages about not being able to find classes that I know are on
>jde-global-classpath, so I started to go through the source code, first of
>jde-wiz.el, then JdeUtilities.java
>
>It looks like this method - and many others that rely on JdeUtilities -
try to
>qualify class names by comparing to the classes reachable through the
environment
>variable CLASSPATH. Is there anyway to connect the value of the CLASSPATH
with the
>contents of the project variables (e.g. jde-global-classpath) ? Or is it
frozen at
>Emacs start-up?
>
You are misreading the code. All the JDE wizards use the value of
jde-global-classpath, if set; otherwise, CLASSPATH. The jde-browse-class
command invokes the Beanshell's browseClass command. Unfortunately, this
command only looks at jar files on the classpath. This is an irritating
limitation that I had forgotten. Perhaps the Beanshell's author will remove
(or already has removed) this limitation. In the meantime, the workaround,
though cumbersome, is to jar any of your own files that you want to browse.
I use it mainly to browse the JDK classes so I'm not that bothered by the
jar file only limitaion.
- 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
