If you’re like me, after a few years of using the same machine, you end up with half a dozen full eclipse installs, with all kinds of plugins scattered around.  A quick check shows I’ve got 3.0, several 3.2’s, 3.4 and the latest and greatest 3.4.1

In the best traditions of less is more, I’ve always tried to reduce these, but then run into various issue.  PyDev is great for Python development, but you always want to keep up with the latest, and it really doesn’t like old eclipse shells.  Apache Directory Studio barfs with the oh-so-common “Wah wah … I don’t like your fancy new JDK” errors.  And when you start throwing in IBM products, you get the joy of package groups as an extra layer of eclipse complexity.

Sooooo, after all this rambling, where am I going with this?  Well, IBM developerWorks has put up a great article on which of its plethora of eclipse-based products can share the same eclipse shell, and lots of walk throughs on how to do it even with other plugins and tools that don’t share nicely.  Check out the article here.  I’m going to attempt to reconcile my 100+ plugins, tools and gadgets into one eclipse shell … I’ll let you know how that goes!