Skip to main content
Jump to: navigation, search

Difference between revisions of "Common Build Infrastructure/Getting Started/FAQ"

m (My build complains it can't find java.lang.Object. Seriously, WTF?)
m (What information do I need to provide to get a new job added to Hudson?)
Line 47: Line 47:
=== What information do I need to provide to get a new job added to Hudson? ===
=== What information do I need to provide to get a new job added to Hudson? ===
To get added to [ Hudson, see [[Common_Build_Infrastructure/Getting_Started/Build_In_Hudson|Build In Hudson]].
To get added to [ Hudson], see [[Common_Build_Infrastructure/Getting_Started/Build_In_Hudson|Build In Hudson]].
[[Category:Athena Common Build]] [[Category:Releng]]
[[Category:Athena Common Build]] [[Category:Releng]]

Revision as of 20:12, 22 July 2009

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) -- how to build -- 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 to generate .psfs from your map files.

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

Make sure you've set JAVA_HOME to a valid path, as well as these for every Bundle-RequiredExecutionEnvironment ("BREE") defined in your plugins. 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


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, 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.

Note that currently, if you include buildExtra.xml or testExtra.xml, only the Eclipse SDK will be unpacked automatically for you. Everything else needs to be unpacked manually in this *Extra.xml file. See bug 284055.

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.

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

To get added to Hudson, see Build In Hudson.

Back to the top