Pack eclipse.equinox.log.jar, eclipse.equinox.htt.jar and eclipse.equinox.event.jar to the file named equinox.additions.zip. The jar files must be placed under eclipse/plugins folder in the zip file. Place the zip file in "build".

Configuring Download Side

Results of each build should be propagated to an http server under DocumentRoot/corona/drops/buildId subdirectory. The folder DocumentRoot/corona must contain the files: build_typese.html, dlconfig.txt and index.php. The files are available in plugin org.eclipse.releng.basebuilder under subfolder builderTemplate\publishingFiles\dropSiteRootFiles\

Troubleshooting Network Configuration

Network access problems.

The setupBuild script uses two types of transport to fetch required resources: cvs and http. Depending on security settings enabled by your system administrator, one or both of there connections can be restricted. Typical solutions are:

for www access: define http_proxy system variable

for cvs access: check which access method is available. cvs can connect to a server using either ext (i.e. ssh protocol) or pserver. pserver access can be used if and only if the user is anonymous. ssh access requires a valid user and a password.

Enabling New Plugins in Build

add the plugin to feature (either org.eclipse.corona.client or org.eclipse.corona.server or both), check for plugin version and unpack option

add the path of the new plugin to map files (corona.client.map or corona.server.map or both)

if required, copy 3rd party jars to the download directory on the build server

Features and maps are located in Corona CVS repository.

Operations Done During Build Phases

Execution of buildCorona script comprises:

cleaning previous build output

fetching build scripts and properties required by the build process such as:

run.bat/run.sh - scripts starting an Eclipse instance as AntRunner

buildCorona.xml - build script file controling the build sequence

customTargets.xml - build script file enabling customization of the build process, defines the map files to be fetched and the features to be built

build.properties - contains the properties needed for fetching and building the sources

executing run.bat/run.sh script

Build Phases

Build Plug-ins (buildAll task)

buildAll task is responsible for building Corona's plug-ins and creating Corona's features.
The most important tasks from this build steps will be described below.

getMapFiles task (customTarget.xml).

This task is responsible for retrieving corona's map files into local build directory. Map files describe the location of corona's plug-in's and features. Location of map files is specified in build.properties file in following section:

logFile - maps compile logs and JUnit test results to a given download.

effectedFile - references the value of the id attribute for a platform element. Used to mark a <platform> with a status depending on the log content.

<build directory>/templateFiles/index.html.template

The template for creating index.html page, this file should contain placeHolders for rows of links to platform-specific and/or platform-independant runtimes for a given download type. Place holders are defined in testManifext.xml file as a zipType name attribute and should be also defined in buildAll.xml file, in publish task as a dropTokenList property.