Eclipse Galileo Improvements to Java Developer Tools

June 19, 2009 at 12:23 am | Posted in Eclipse, Java | 2 Comments
Tags: , , ,

Here are some improvements to JDT Project in Galileo that I personally find useful:

  1. Support for {@inheritDoc} in the javadoc popups.
    • This is encourages its use, which in turn encourages documenting why a method has been overridden, or what’s so special about this particular implementation, without having to repeat the purpose of the method itself.
  2. Warnings when a method overrides a synchronized method, but isn’t synchronized itself.
    • It’s hard enough as it is to ensure you get the intended multi-threaded behaviour. This change can help prevent an error that while not very common, can be very hard to spot.
  3. When auto-reformatting an entire class, I can keep the line breaks that I’ve added.
    • This caters for where the formatting rules are too general, and are not aware that I’d find some things much clearer if split into multiple lines in very specific places.
  4. Constructor completion has been made more useful, by offering more appropriate suggestions.
    • I also often save myself some typing by writing the right hand side of the assignment, then using a quick assist to assign the result to a new variable.
  5. By holding down Ctrl, and hovering on a method, I can chose whether to jump to the declaration, or the implementation.
    • I still find this method of navigation difficult though, preferring to keep my hands on the keyboard, navigating to the method call, pressing Ctrl-T, and choosing which implementing or declaring class I wish to view. (That’s not a new feature.)
    • What I’d like is a companion for F3’s mapping of “Go To Declaration” that with a single key press I can “Go To Implementation”. However I can’t find that command in the key binding preferences page.


  1. “When auto-reformatting an entire class, I can keep the line breaks that I’ve added.”

    Cool. I was just searching for whether it was possible to do this with ganymede, but I guess you’ve just answered my question. I’m amazed it took so long, it’s such an obviously useful feature.

  2. If you’re going to use the setting to never join lines needs, you do need to also fine tune how you’ll let eclipse break lines, since otherwise it’ll quite happily do things like convert a multi-line comment into 1 long line then a line with 1 word, the another long line, then another line with 1 word, etc.

    What would be useful would be if you could select a portion, and reformat, chosing whether to allow line breaking and joining or not.

Sorry, the comment form is closed at this time.

Create a free website or blog at
Entries and comments feeds.

%d bloggers like this: