This problem will probably occur with other languages too where you need to let a statement span several lines. Even if there is no argument list, you usually want to indent the continuation lines with respect to the first line, but then have the next statement indented under the beginning of the first line of the previous statement. So the parser *has* to take care of more than one line (well actually it only needs to keep a couple of numbers and flags up-to date, but I do not know how this is implemented).

The problem is that there is no acceptable workaround really: I currently manually insert a comment under the long statement and hope to never touch that. But this is a shortcoming that probably demotivates me enough to go back to xemacs

One option is turning off deep indent until it gets fixed. I wrote the first deep indent patch, so I'm looking at fixing the problem now.

with deep indent off, no indentation whatsoever is performed which is wrong either ... continued statements should at least get one level of indent. And *if* I fix that so that there is one level of indent, then the next statement is again wrongly indented below this.
It seems that indenting is simply done in a much too naive way. Indentation should at least know what a statement is and where the last statement begun - even if it was several lines earlier.

Anyways, looking forward to any improvement and thanks for the reply!

I sent slava a patch a couple days ago (you saw it if you happen to be on the jedit-devel list) which fixes the problems you mentioned with deep indent as well as a fix to regular indenting where something like

public void something(int a,
                      int b) {
    System.out.println("hello");
                      }

would happen.