Skip to main content
Jump to: navigation, search

A Brief Overview of Building at Eclipse

Revision as of 17:24, 3 November 2008 by (Talk | contribs) (PDE Build)


This page is about building Eclipse- and RCP-based products (including Eclipse itself). This document is focused on using PDE Build directly; work is currently underway to develop a Common Build Infrastructure.

PDE Build

PDE Build is The Way to headlessly build Eclipse- and RCP-based products. The online documentation provides a good foundation of knowledge, but does fall short in on some specifics, including the use of Pack200 and JAR signing using the Eclipse Foundation's certificate. This document addresses these issues.

The best currently available guide to PDE Build is still Markus Barchfeld's Build and Test Automation for plug-ins and features, though it's getting a bit old (having been written for eclipse-3.0). The Eclipse IDE for Education project's releng project provides a relatively simple example of how PDE Build can be used to build, Pack 200, sign, and create an update site using the Eclipse Foundation's build server.

Build Server

Eclipse projects can use the Eclipse Foundation's build server to run automated builds. To gain access to the build server, your project lead should send a note to the Eclipse Webmaster.


Eclipse itself is built using the PDE build infrastructure that it ships with the Plug-in Development Environment. Ant is used to run the build, with adequate plug-points where in you can perform custom tasks such as instrumentation of code.

To get comfortable with ant:- - If you are new to ant

Eclipse provides a very usable interface for writing ant files(yes, with auto-complete and the stuff) as well as run the ant files from within the IDE. But, for headless(without UI, from command line) builds, you'll need to use the antRunner application provided by eclipse. For more help, peek into the help documentation of eclipse that you are using.

Plugin Builder plugin - Something to make your life even easier

You might get stuck nowhere:-


Plugins (including features and fragments) must specify their own versions as well as the versions of their dependencies appropriately.


See the eclipse team's plugin-versioning guidelines. You can also ask Pascal Rapicault or John Arthorne for their "Plug-in versioning" presentation.


Pascal Rapicault has created an application (org.eclipse.core.runtime.versionchecker.dependencyChecker) to "specify the ranges on all [your] required plug-ins."

Cross-platform build

Eclipse RCP applications can be cross-built for several platforms using any platform on which eclipse runs. You just need to install the RCP delta pack in your Target Platform. If you dont know what a Target Platform is, then just intall the RCP delta pack in your eclipse installation directory. To download the delta pack as per your platform, visit Click the Release version that you are targeting, then search for 'delta'.

Back to the top