Eclipse optimizations

Question

The question dealing with Visual Studio optimizations saved me so much time firing it up and using it I have a hard time going back to Eclipse when I have to do J2EE develop

Answer 1

The cheapest and fastest optimization I ever did for Eclipse is to buy extra 2G of RAM for my dev machine.

Answer 2

if you are looking to remove the sluggishness from the app, memory management is obviously important. besides increasing the maximum heap settings and other command line tinkering, there have been eclipse plugins developed in the past that claim to prevent windows from swapping out eclipse RAM. 'Keep Resident' hasnt been updated since 2004, but it is still on the eclipse site and i have heard tell that it works with 3.4. a review is written here

Answer 3

I think the best way to learn about eclipse shortcuts is to use MouseFeed. MouseFeed is a plugin which shows the corresponding shortcut keys whenever the user uses the mouse to perform some actions. Common tasks and the shortcuts for them can be acquired within a few days. Mousefeed can be found at http://www.mousefeed.com/. Hope this helps.

Answer 4

Eclipse has LOTS of shortcuts, but most of them are not straightforward. E.g.: shift-alt-X, then T to run a JUnit test.

Sometimes you just need to try and see if it works.

I found the editor arrow-key-macros particularly useful, but you need to play with them yourself to understand it: alt+shift+{left,right} to select an expression for refactoring, ctrl+alt+down to duplicate a line, ctrl-shift-{up,down} to jump to previous definition...

The most powerful combinations are usually the alt-shift-something (especially for refactoring).

Look for "eclipse cheat sheets" on google to find some more inspiration.

Answer 5

There are:

• system optimizations: eclipse.ini
• shortcuts optimizations:
  • Quick Access (Ctrl+3) (the mother of all shortcuts! With it, you can access almost everything in Eclipse)
  • Quick Fix (you should make sure it has a convenient shortcut attached to it)
    
    (that includes Run or Debug configurations available in your workspace since 4.12)
• launchers optimizations : save them with your projects and do not forget to uncheck the option "Delete configurations when associated resource is deleted" in the "Run/Launching/Launch Configuration" preference panel:

And then there are the configuration of:

• project preferences
• perspectives (which you can configure across multiple screens)
• provisioning mechanism p2 (with bundle pools to share plugins across multiple eclipse installations)

Answer 6

The biggest optimization I've found for Eclipse is turning off Theming. My very minimal installation was extremely slow, so I wasted a ton of time doing all the debugging steps until I finally unchecked "General > Apperence > Enable theming" and everything got much much faster. I also put -server in my eclipse.ini, but, the biggest trick was just turning off theming (with much much sadness).