Building Eclipse distributions in your own PC or in your company server is an important goal of the Eclipse CBI initiative and more broadly an important step of providing the LTS services around Eclipse technologies.
LTS means that companies will be able to provide Long Term Support and maintenance which requires a way to build a given Eclipse distribution from sources as easily as possible. This is where CBI comes in. Using maven, Hudson and Tycho it aims to make it possible to build the Eclipse distributions (the ones you can download from the official download page) with a one-click effort. The first step toward this is to shape the actual sources and build metadata in order to build the SDK as a normal maven build, a “mvn clean install” command.
As a result of the work of the Platform and CBI team this is now possible and the Eclipse I’m using today was built yesterday in the same PC.
It is important to note that there is some additional work to be done in order to provide a General Availability mechanism with security signing etc. but building a working version is a major advance (and feels good if you are a geek).
What you need to have is just git (command line), maven 3, a JDK (won’t work with a JRE) in your JAVA_HOME and some 15GB disk space to spare. The full guide is here http://wiki.eclipse.org/Platform-releng/Platform_Build . Basically you go through setting stuff up, cloning the source, building a parent pom and then the do the main build. The process is relatively simple if you are used to maven and git and the part requiring your attention should not be more then half an hour. If you want to go deeper the guide supplies more details to do other things (signing, running tests, specific natives build etc).
There is a bug relating to a mirror being down so, until the bug is fixed, BEFORE getting into the Running the build section in the wiki you need to download and apply a simple patch: (supposing you are in the /eclipse.platform.releng.aggregator folder)
git apply C:/path/to/patch
After that things should run smoothly and after some 2 hours of maven doing its work (depends on the machine power) you will have the Eclipse distributions in your machine.
As a next step I plan to integrate this with my local Hudson and run Sonar analysis. This “mavenization” of the build opens up a wide range of possibilities.