Oh, I see you already found the mailing list so I will copy my answer
here for all to see.
> * When I compile with AntFarm, I used to get a red marker on the
> vertical scroll bar for each error location. It was very usefull, but
> it's gone.
I don't know about
> * SOLVED: The StructureBrowser for Java sources showed a full
> signature of a method, down in the status line, but the Sidekick,
> which I believe uses JavaSideKick, doesn't show method arguments.
I don't know which StructureBrowser you mean, but yes, JavaSideKick is a
service provider for SideKick and in its properties you can set up what
you want to see. I see full method signatrues in my SideKick.
> * Question: why do we have Beauty and JavaStyle plugins if they do
> the same for Java?
Ask the creators, the most plugins are from contributers, not from the
core team. I guess JavaStyle was built earlier and then Beauty came as a
framework for several languages, not only Java. Additionally JavaStyle
is rather old, I don't know if it even still works.
> * JSwatPlugin plainly doesn't start and shows an error about a
> TextArea.getBuffer() not found. Is JSwatPlugin dead? It's the only
> debugger in this jEdit version and also it's a good debugger (except
> for some glitches).
Maybe it is not compatible with the current API changes. This should be
reported to the JSwat project, maybe it gets fixed. Maybe, because JSwat
changed its internal structore completely and got rewritten to fit into
the NetBeans plugin architecture and the author didn't/doesn't make any
effort to make the current JSwat version available as jEdit plugin. I
use JSwat as standalone version. Maybe if I ever find the time I will
look if I can make a JSwat plugin that works with current JSwat, or
maybe you want to do it? Be welcome :-)
> * ERROR: once a while, the whole jEdit gets into some error
> condition, takes all CPU, and although it functions, there is no way
> to bring it back to be a nice citizen, but to restart it. This
> happens just while editing.
Without a reliable way to reproduce and more information like errors in
the Activity Log or something, it isn't determinable what your problem is.