Jump to: navigation, search

Common Build Infrastructure/Getting Started/FAQ

< Common Build Infrastructure‎ | Getting Started
Revision as of 08:03, 2 September 2009 by Stephane.bouchet.obeo.fr (Talk | contribs) (My build complains it can't find java.lang.Object. Seriously, WTF?)

What files do I need to run an Athena build?

In some folder, traditionally called org.eclipse.myproject/releng or org.eclipse.myproject.releng (but really, it can be anything), you need these files:

maps/*.map -- what to build (where to get sources) : can be CVS, SVN, or HTTP (eg., Orbit jars)
build.properties -- how to build
testing.properties -- what tests to run
build.xml -- boilerplate script for running the build in Eclipse, via commandline, or in Hudson

I also recommend having a .launch file which produces a log of your in-Eclipse build attempts so that when that log scrolls off the Console view, you can see what happened in the file.

And, if you want to make it easier for others to get your source, you can include psfs/*.psf files. Better, use build.steps=map2psf in your build.properties to generate .psfs from your map files.

My build complains it can't find java.lang.Object. Seriously, WTF?

First, make sure EVERY plugin you're building has a Bundle-RequiredExecutionEnvironment defined. If not, PDE will thing you're trying to build Java 1.2 or 1.3 code, and your Java 5 annotations will fail to compile.

Next, in your .releng project's build.properties file, make sure you've set JAVA_HOME to a valid path, as well as setting a valid path for every Bundle-RequiredExecutionEnvironment ("BREE") defined in your plugins' MANIFEST.MF files. If all your code is set to BREE 1.4, you only need a JAVA14_HOME; if you have a mix, include all that you use, such as JAVA50_HOME or JAVA60_HOME.

Here are the default values for these server.properties:


Finally, note that if you're running on a 64-bit OS with a 64-bit Eclipse, you need a 64-bit JVM.

What are buildExtra.xml and testExtra.xml for?

These are optional.

If you have custom runtime requirements which cannot be configured using dependencyURLs or repositoryURLs in your build.properties, you can define additional fetching/unpacking steps here, for building or testing respectively.

If you have custom packaging steps (ie., you ship more than the default set of zips) you can also add packaging steps here.

${org.eclipse.test} not found?

1. Include "org.eclipse.test" and "org.eclipse.ant.optional.junit" plugins in your all-in-one tests feature (or to each test feature). This controls what plugins PDE will build.

  download-size="0" install-size="0" version="0.0.0"/>
  download-size="0" install-size="0" version="0.0.0" fragment="true"/>

2. Add these plugins to your map file (or create a new map file). This controls where PDE will find the Eclipse Test Framework (ETF) sources.


Do I still need a test.xml in each of my test plugins?

No. In fact, having one there may cause some of your tests to fail. Omit this file and one will be generated for you from this template.

How do I build source features / plugins?

Three touchpoints are required:

1. In your .releng project's build.properties, set:


2. In your runtime feature, define templates for features/plugins to be generated:


3. In your SDK or "all-in-one" feature, define how to generate the feature / plugin:


See also PDE Build > Generating Source Features and Plug-ins.

What information do I need to provide to get a new job added to Hudson?

To get added to Hudson, see Build In Hudson.