The error remained even after we added jedit.jar to the build path.
Can you tell us the step-by-step procedure of how to build the .jar file of the plugin with debugging information? Then, probably, we could do what you said, i.e. start jedit and debug it remotely. Also, in that case, jedit will stop at breakpoints only after we attach the debugger and so we won't be able to debug functions called at startup. Is there a workaround for this?
You'll need to start jEdit in a JVM session that
has remote debugging enabled, and then start a
remote debugging session. I posted step-by-step
instructions for doing this in Eclipse a few
months back in the (little used) jEdit Community
Here's the post:
--- Sagar Rastogi <firstname.lastname@example.org> wrote:
> I am a newbie to both Java Swing and also Jedit. I
> need to customize the
> Lazy8Ledger plugin. How do I set breakpoints in its
> I've been able to set breakpoints in the code of
> jedit but since it loads
> the .jar file directly for plugins, how do I debug
> Is there an IDE which I can use from which I can
> edit, build and even debug
> the plugins?
Yahoo! Mail - PC Magazine Editors' Choice 2005