Useful Eclipse features?

Eclipse

Eclipse Problem Overview


I have been using Eclipse as an IDE for a short amount of time (about 3 months of full use) and almost every day I learn about some shortcut or feature that I had absolutely no idea about. For instance, just today I learned that Ctrl+3 was the shortcut for a Quick Access window.

I was wondering what your most useful/favorite Eclipse features are. With the IDE being so big, it would be helpful to learn about the more commonly used parts of the program.

Eclipse Solutions


Solution 1 - Eclipse

My most commonly used features are

ctrl+1 quick-fix / spell-checker

opening files

  • ctrl+shift+t load class file by classname
  • ctrl+shift+r load any file by filename

matches are made on the start of the class/filename. start your search pattern with a * to search anywhere within the filename/classname.

Formatting

  • ctrl+shift+f Format source file (set up your formatting style in Window | preferences | java | code style | formatter)
  • ctrl+shift+o Organise imports

Generated code

  • alt+s,r to generate getters and setters
  • alt+s,v to insert method signatures for overidden methods from superclass or interface

Refactorings

  • alt+shift+l Extract text-selection as local variable (really handy in that it determines and inserts the type for you.
  • alt+shift+m Extract text-selection as a method
  • alt+shift+i inline selected method

Running and debugging.

alt+shift+x is a really handy prefix to run stuff in your current file.

  • alt+shift+x, t run unit tests in current file
  • alt+shift+x, j run main in current file
  • alt+shift+x, r run on server

There are more. The options are shown to you in the lower-right popup after hitting alt+shift+x.

alt+shift+x can be switched for alt+shift+d in all the above examples to run in the debugger.

Validation

As of the recent Ganymede release, you can now switch of validation in specified files and folders. I've been waiting for this feature for ages.

  • Go to Project | Properties | Validation
  • click on the ... button in the settings column of the validator you want to shut up
  • Add a rule to the exclude group

code navigation

  • hold down ctrl to make all variables, methods and classnames hyperlinks to their definitions.
  • alt+left to navigate back to where you clicked ctrl
  • alt+right to go "forwards" again

Solution 2 - Eclipse

This is cool: If someone has emailed you a stack trace, you can copy and paste the stack trace into Eclipse's Console window. You can then click on class names in the stack trace as if your own code had generated it.

Solution 3 - Eclipse

Ctrl-Alt (up/down) Copy selected line(s) above or below current line.
Alt (up/down) Move current (or multiple selected) lines up or down
Ctrl-Shift-R Bring up the resource window, start typing to find class/resource
Ctrl-O Bring up all methods and fields for the current class. Hitting it again will bring up all methods and fields for current class and super classes.
Ctrl-/ or Ctrl-Alt-C Comment single or multiple lines with //
Ctrl-Shift-/ Comment selected lines with /* */
Ctrl-. Take you to the next error or warning line

Solution 4 - Eclipse

In terms of actual features, rather than shortcuts, I strongly recommend taking a look at Mylyn.

It essentially skins Eclipse with a task focussed view. It tracks the files you touch when working on a task, and focusses many aspects of the UI onto the resources that it decides are relevant to the job in hand. Eclipse can be somewhat busy to look at, especially with a big multi module project, and Mylyn helps cut through the cruft. The connectivity to issue tracking software and source control repositories is also excellent.

In my experience, it polarises opinion amongst those who try working with it, which is probably a sign that it is offering something interesting... Don't mean to sound like a fanboy - it is definitely worth a look though.

Solution 5 - Eclipse

A shortcut that I use everyday is Ctrl+K. In your editor (not only Java file), simply select a text (like a variable, a function, etc.), and then use this shortcut to go to the next occurrence of this text in the current editor. It's faster than using the Ctrl+F shortcut...

Note also that you can use Ctrl+Shift+K to search backwards.

Solution 6 - Eclipse

CTRL+PAGE DOWN / CTRL+PAGE UP to switch between opened editors

CTRL+E to also switch between opened editors (allows to type the name)

CTRL+O is extremely important for me. You don't longer need the Outline View then (you can close it which will give you more space). Then, you can type a method name or just the beginning of it and you quickly can get to it. I also use it to inspect what stuff is available. For example: CTRL+O and then type get ... now I see all getters.

F3 while an element is selected in the code: brings you to its definition or it's source. e.g. used on a method call it brings you into the source code of that method.

CTRL+M to maximize the current window

As already said, CTRL+3 is extremely good. It basically allows you to use Eclipse completely without a mouse. Just type CTRL+3 and then package explorer for example.

CTRL+F8 cycle trough perspectives

CTRL+L allows to type a line number and brings you directly to that line.

CTRL+SHIFT+G searches for all references to the selected element in the workspace.

And not a shortcut: In the project settings under Java Editor you can find Save Actions. This allows you to set up the project so that the code is automatically cleaned up and formatted when you save a file. That's very good it safes you from constantly pressing CTRL+O and CTRL+F.

Solution 7 - Eclipse

Eclipse auto refresh isn't on by default so if you make changes to a file outside of eclipse, the change won't be reflected in your build. this is very annoying if you just did an svn/git update/rebase and things aren't working the way they're supposed to.

Turn it on in windows->preferences->workspace and tick Refresh Automatically.

Solution 8 - Eclipse

Local History

It's a great feature. Eclipse has its own mini-CVS for all files in a project. If you want to revert some change you made, or even restore deleted file - you can right click on the project and select "Restore from Local History".

Just saved my ass *tears of joy*

Solution 9 - Eclipse

CTRL+Shift+P to jump to the matching bracket/parenthesis.

Solution 10 - Eclipse

One key feature: Shift+Alt+T for the refactoring menu.

Solution 11 - Eclipse

  • Ctrl-shift-T, but only type the initial characters (and even a few more) of the class you're looking for. For example, you can type "NetLi" to find NetworkListener

  • In the Search window, Ctrl-. takes you to the first leaf of a tree branch

  • Alt-/ is Word Completion. Slightly different from Ctrl-space

Solution 12 - Eclipse

A lot of the key bindings depend on the perspective and view currently active.

My most used ones for the Java perspective:

  • ctrl-shift-r open resource
  • ctrl-shift-t open type
  • ctrl-1 quick fix/refactor
  • ctrl-j incremental search
  • ctrl-h search in files (select a base directory and set scope to selected resources)
  • ctrl-o list methods
  • ctrl-alt-h open call hierarchy
  • ctrl-shift-l list shortcut keys
  • hit ctrl-shift-l again to go directly to preferences to change key mappings

Solution 13 - Eclipse

I'd like to add two additional shortcuts:

  • CTRL+F6 Switch between open editors (CTRL+SHIFT+F6 to scroll through the list in the opposite direction)

  • CTRL+F11 start program in debug mode

  • F11 start program in normal mode

Solution 14 - Eclipse

  • CTRL+SHIFT+X selected text becomes UPPERCASE

  • CTRL+SHIFT+Y selected text becomes lowercase

Solution 15 - Eclipse

I am also a fan of Eclipse, however since I spend a majority of my time in Visual Studio, I will suggest that you read Eric Sink's series of articles "C# to Java" (parts 1-4). Not only is Eric always an entertaining read, but this brief series covers some awesome Eclipse insight for those who have not been into Eclipse or have been away from it for a while:

From C# to Java: Part 1
From C# to Java: Part 2
From C# to Java: Part 3
From C# to Java: Part 4

Solution 16 - Eclipse

Ctrl-Shift-M while the cursor is on a class name in your java file, will specifically add that and only that class to your imports. This is different from Ctrl-Shift-O which will not only add those imports not already defined, but will also remove imports not currently needed, something you might not necessarily want to do.

I forgot about [Ctrl+2 -> r] scope variable rename. Place the cursor in the variable you wish to rename, press Ctrl+2, then r, then type the new name watching all instances of that variable get renamed at the same time.

It's awesome at refactoring Hungarian Notation.

Solution 17 - Eclipse

alt-shift-a is extremely useful in a few situations.

Solution 18 - Eclipse

I use a lot of the above and also like for quick search: CTRL+J then type what I am looking for, then CTRL+K for next occurrence.

Solution 19 - Eclipse

Shift+Alt+b for the simple navigation row over the editor.

Solution 20 - Eclipse

Lately I've been using the MouseFeeds plugin to automatically tell me what the key stroke combinations are. That way by repetition I remember them better.

This link has a better picture and description of what it looks like and does.

Solution 21 - Eclipse

I've just released this blog post about Top 5 Useful Hidden Eclipse Features. It contains:

  1. Favorites: Types and members that will always show up in auto-completion
  2. The awesome block selection mode: For multi-line editing
  3. The EGit staging view: Much better than git itself
  4. Type filters: To remove awt and java.lang.Object stuff from auto-completion
  5. Formatter tags: To delimit code sections that shouldn't be auto-formatted

Solution 22 - Eclipse

Alt+left and Alt+ right will navigate you forward and back.

Solution 23 - Eclipse

I find the project-specific settings useful in Eclipse 3.3.

For example, if you have several developers working on a project who have different code styles for curly braces, line spacing, number of imports etc. then you can specify the style settings for the project. Then you can configure the save actions so that the code is automatically formatted when a file is saved. The result is everyone's code is formatted the same before it's checked in.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionAdam MikaView Question on Stackoverflow
Solution 1 - EclipseCheekysoftView Answer on Stackoverflow
Solution 2 - EclipseDavid KoelleView Answer on Stackoverflow
Solution 3 - EclipseN8gView Answer on Stackoverflow
Solution 4 - Eclipseserg10View Answer on Stackoverflow
Solution 5 - EclipseRomain LinsolasView Answer on Stackoverflow
Solution 6 - EclipseAlexView Answer on Stackoverflow
Solution 7 - EclipseCharles MaView Answer on Stackoverflow
Solution 8 - EclipsesergView Answer on Stackoverflow
Solution 9 - EclipsekarlphillipView Answer on Stackoverflow
Solution 10 - EclipseabyxView Answer on Stackoverflow
Solution 11 - EclipseDavid KoelleView Answer on Stackoverflow
Solution 12 - EclipseDavid SchlosnagleView Answer on Stackoverflow
Solution 13 - EclipseJohannes K. LehnertView Answer on Stackoverflow
Solution 14 - EclipselostinicelandView Answer on Stackoverflow
Solution 15 - EclipseIan Patrick HughesView Answer on Stackoverflow
Solution 16 - EclipseSpencer KormosView Answer on Stackoverflow
Solution 17 - EclipseCromTheDestroyerView Answer on Stackoverflow
Solution 18 - EclipseoshaiView Answer on Stackoverflow
Solution 19 - EclipseJakubView Answer on Stackoverflow
Solution 20 - EclipseJames DrinkardView Answer on Stackoverflow
Solution 21 - EclipseLukas EderView Answer on Stackoverflow
Solution 22 - EclipseJeevsView Answer on Stackoverflow
Solution 23 - EclipseMichael SharekView Answer on Stackoverflow