Why do EMF and Xtext build with Buckminster?

Session Type: 
Standard [35 minutes]

At a first glance it is easy to build Eclipse projects. The naive approach is to import them into your workspace and the Eclipse builder takes care of the rest. In the blink of an eye everything is compiled, ready to be exported. Turns out the approach is not too naive at all. The real question is why building that very same code base on an integration server has proven to be such a nightmare in the past? Shouldn't that be equally simple? This is where Buckminster comes into the picture. The philosophy behind it is striking: the integration server's build is the very same as in the development environment on your local machine. Reasonable, isn't it?

In this session we will give a short overview on Buckminster and demonstrate why popular Eclipse projects such as EMF or Xtext chose to use it in these times of the new Maven-Tycho-based effort to create a common build infrastructure (CBI) at Eclipse. Given a small Xtext project, we will setup the complete tool chain from sources in a git repository to a Hudson build that produces a deployed update site. You will learn about the advantages of a single-sourced build configuration. Be it the project's compiler settings, the launch configurations for your unit tests, or the API tooling, everything works on the server just as it does on your machine. And if you are still in doubt about the value of the Buckminster project, we will use some real world examples to show the scalability of this approach.

Schedule info



Experience level: 

Copyright © 2013 The Eclipse Foundation. All Rights Reserved.