Eclipse Workspaces with Oomph

Oomph is not only about eclipse installation, it changes also the way you organize your workspaces.

Multiple Eclipse installations

In my previous blog post I have explained why you can have as many eclipse installations as you want (an installation is 20 MB, the bundle pool is shared and maintenance like updates can be automatized). This solves another problem I had: I have a lot for workspaces and I never knew with which eclipse I should open it.

The basic Idea is simple: a workspace containing a scout application should be opened with “Eclipse for Scout Developers”. My Xtend experimentations should be opened with “Eclipse IDE for Java and DSL Developers” and so on… But when you start to have several versions of each IDE (if you consider some of the Milestone releases, there are a lot of Eclipse versions) you have no chance to remember it properly.

It gets worth when I try something different. I need to remember in which version of the “Eclipse Modeling Tools” I did install the MoDisco plugins to try this project out… (Was it Luna? Was it Mars?). The same goes for the Eclipse B3 tools I have installed this tool to create a maven repository for Mylyn Wikitext. Where did I install it? It is a mess!

The Oomph way

When you start to work with Oomph, you control where Oomph will install and checkout all the components needed for the setup. What is particularly interesting is that you can work with patterns that are reused for each of your installations. I have decided to stay with the default setting:

  • Installation location rule: “Installed in a uniquely-named folder inside the root folder”.
  • Workspace location: “Located in a folder named 'ws' within the installation folder”.
  • Git clone location rule: “Located in a folder named 'git/<repo>' within the installation folder”. 

With those settings, the structure I get for each of my installations is the same:

Datum