[FAQ Candidate]: Can I modify the classpath of a macro?
Submitted by Tuesday, 12 October, 2004 - 10:53
on
Hi all,
Can I modify the classpath of a macro?
It seems that my question have to be inserted in jEdit FAQ.
------------- References from previous discussions
[1] Using external java libraries in macros 1 05/01/2004 - 6:38am
by AndreJRenard 05/03/2004 - 8:30am
by Brad Mace
[2] How do I modify the classpath of a macro? 0 04/09/2004 - 4:09am
by Anonymous
-------------
The only solution suggested in previous discussions by Brad
was to put my jars into jEdit folder.
That's good, but not too handy. BeanShell's addClassPath() command was
much better.
Currently I have my classes compiled in Eclipse workbench and can play
with them from BeanShell script as much as I like. I run my BeanShell scripts
from command-line currently and I hoped that jEdit's BeanShell Console can be
a better tool.
Changing class in Eclipse is enough for script. But if I had to create jar,
put it into jEdit folder and restart jEdit to catch the changes, it makes it
useless.
My suggestion is to reflect this behaviour in jEdit FAQ.
Best regards,
Egor Abramovich
egor_abramovich@mail.ru
Can I modify the classpath of a macro?
It seems that my question have to be inserted in jEdit FAQ.
------------- References from previous discussions
[1] Using external java libraries in macros 1 05/01/2004 - 6:38am
by AndreJRenard 05/03/2004 - 8:30am
by Brad Mace
[2] How do I modify the classpath of a macro? 0 04/09/2004 - 4:09am
by Anonymous
-------------
The only solution suggested in previous discussions by Brad
was to put my jars into jEdit folder.
That's good, but not too handy. BeanShell's addClassPath() command was
much better.
Currently I have my classes compiled in Eclipse workbench and can play
with them from BeanShell script as much as I like. I run my BeanShell scripts
from command-line currently and I hoped that jEdit's BeanShell Console can be
a better tool.
Changing class in Eclipse is enough for script. But if I had to create jar,
put it into jEdit folder and restart jEdit to catch the changes, it makes it
useless.
My suggestion is to reflect this behaviour in jEdit FAQ.
Best regards,
Egor Abramovich
egor_abramovich@mail.ru