Skip to main content
Jump to: navigation, search

Common Build Infrastructure/Defining Binary Dependencies

There are multiple ways to define your dependencies when doing an Athena build. Below are examples which can be used in your file.

Note that instead of http:// or ftp:// paths, you can also specify /path/to/ Once a zip has been fetched from remote, it will be cached in your downloadsDir for reuse. By default, this will be /tmp/build/downloads/.

SDK or Runtime Zips

By default, everything listed in dependencyURLs will be installed automatically. Should you want to override this behaviour, you can define your own buildExtra.xml or testExtra.xml and inject custom steps for unpacking dependencyURLs. Zips containing "master" or "update" in their name will be treated as update sites; all others will be unpacked into eclipse/dropins/.

# CDT master zip is an update site zip w/ p2 metadata and site.xml

Update Sites

Remote Site

Provisioning directly from an update site may fail due to socket timeouts; however, this method can work when the network is cooperative.


Or, specify multiple update sites:


With Eclipse 3.5M7+, you can do multiple provisioning installs in a single p2 operation. Note the use of "+" to define which feature.groups to install together. You can still use commas to define sequential operations.


Remote Zipped Site

As noted above, you can use update site zips as dependencyURLs. However, it's probably better to set them as repositoryURLs since that is what they are. Using the prefix will fetch the specified zip from the mirror deemed to be closest to your IP address, unpack it, and if necessary, generate p2 metadata from the included site.xml file.


More information

Back to the top