Oomph: Eclipse the Way You Want It
12Consider the manual tasks needed to set up a fresh Eclipse development environment the way you want it:
Download an Eclipse package.
Which package has the features you need?
For that package, do you have a JVM of sufficiently high version, e.g., Java 1.7, and appropriate bitness, i.e., 32 versus 64?
Unpack the download and run the executable.
On Windows, which tool can you use to unpack the download?
Which JVM does the executable use by default and what if that's not the right one
Assuming you get this far, you'll have a blank new workspace, and you'll generally need to do many more things:
Install additional tools.
Set various preferences, most of which you'll need to set yet again for each and every new workspace you ever use.
Fetch, from one or more source code repositories, the projects with which you want to work.
Materialize a target platform to compile and run your source projects.
With Oomph all these tasks are formalized, e.g., p2 tasks to install features, preference tasks to set preferences, and so on. In this workshop you will learn about Oomph's architecture. You will leave with a good understanding of how to author a fully automated script that always produces an Eclipse development environment exactly the way you want it.