Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Corona/Releng/Build"
(→Steps required for setting headless build platform) |
(→Stages of build process) |
||
| Line 40: | Line 40: | ||
inside the build.properties). | inside the build.properties). | ||
| − | == Stages of | + | == Stages of build process == |
*preBuild - fetching and concatenating map files (in corona.map dynamic setting of cvs tag name is made on the basis of fetchTag property value defined inside build.properties) | *preBuild - fetching and concatenating map files (in corona.map dynamic setting of cvs tag name is made on the basis of fetchTag property value defined inside build.properties) | ||
*fetch - retrieving project resources on the basis of the map files definition | *fetch - retrieving project resources on the basis of the map files definition | ||
Revision as of 08:54, 24 May 2006
| Eclipse Home | Wiki Home | Development |
Contents
Installation and configuration of headless automated build process for Corona
For headless build the infrastructure provided by the PDE and the RelEng (Release Engineering) plugins is needed. To create an environment needed for the build process the seperate org.eclipse.releng.basebuilder plugin is sufficient however the Eclipse SDK can be used as well (Corona requires 3.2 version of Eclipse environment).
Build prerequisities
- CVS client version 1.10 or higher on system path
- Info-Zip zip and unzip executables on system path
- JDK 1.4.x (or newer) installation
Steps required for setting headless build platform
- download buildCorona.bat for windows platform or buildCorona.sh for linux platform
- set the following properties from buildCorona.bat/buildCorona.sh to reflect the build environment:
- set JAVA_HOME to point at the JDK installation
- set eclipseDir to point at the Eclipse installation to be used for the build
- set buildType to receive server or/and client Corona distribution, supported values for this property: client, server, full
- execute the buildCorona.bat/buildCorona.sh file to build Corona project.
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
Results of successful build process
${buildDirectory}/buildResults directory (buildResults name is a value of buildLabel property defined inside the build.properties) contains zip archive(s) with corona distribution. For 'buildType=full' two archives are created: org.eclipse.corona.client-DEMO.zip and org.eclipse.corona.server-DEMO.zip (DEMO name is a value of buildId property defined inside the build.properties).
Stages of build process
- preBuild - fetching and concatenating map files (in corona.map dynamic setting of cvs tag name is made on the basis of fetchTag property value defined inside build.properties)
- fetch - retrieving project resources on the basis of the map files definition
- generate - generating build scripts for fetched resources
- process - compiling sources, coping results to build output directory or creating jar files containing the build output
- assemble - creating zip archive containg all build results