Since Eclipse slows down when the number of plugins increases, I usually start with the naked Java package and install some missing plugins (Help –> Install new software) from the Indigo site (another way is to use the JavaEE package and remove the datatools):
- WTP (Group “Web, XML,…”) [TODO which packages exactly?]
- Eclipse Plug-in Development Environment (Group “General purpose tools”)
...needed by UCDetector (see below) - Subversive SVN Team Provider (Group “Collaboration”)
...but only if I am forced to use SVN. I prefer this one over Subclipse because it integrates with Mylyn. On the “connector” dialog I usually choose JavaHL 1.6. On big projects, I use only the history/compare function - update/merge/commit is too slow and should better be executed via commandline or TortoiseSVN.
- TestNG (update site)
...though I really prefer JUnit (because IMO TestNG violates the KISS principle) - Unused code detector (update site)
...a great tool to discover orphan code - Jadclipse (update site)
...automatically decompiles libraries that have no sourcecode attached - but conflicts with the Maven plugin that tries to download the sources (which sure is preferred) - AspectJ Development Tools (update site)
I wouldn't use AspectJ in production code (I don't like AOP alltogether), but it is a nice way to e.g. enforce architecture rules during development
- Sonar (update site)
- jBPM process designer [TODO link]