Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
RAP/Build Process
Since version 1.5, RAP is built on the public build server at Eclipse.
Contents
Hudson Builds
We have two build jobs at the Eclipse.org Hudson:
The base directory for our builds is /shared/rt/rap
on build.eclipse.org
.
Nightly Builds
We produce a p2 repositories from our nightly builds:
- http://download.eclipse.org/rt/rap/nightly/runtime/
- http://download.eclipse.org/rt/rap/nightly/tooling/
These p2 repositories are updated by a cron job:
/shared/rt/rap/scripts/1.5/updateNightlyBuilds.sh
This job is run by rsternber's crontab.
Procedure for Milestone builds
- Tag CVS
- Tag everything that is contained in the
rt/org.eclipse.rap
module, pattern:vYYYYMMDD_R12-Mx
- You may need to increase the CVS connection timeout in Preferences -> Team -> CVS -> Connection tab (120 s seem to work)
- Tag everything that is contained in the
- Prepare new base platform in
/shared/rt/rap/base-platforms
(see/shared/rt/rap/README
)- Copy base platform, extract it into a new directory
- Copy
com.ibm.icu.base
and include the bundles into the base platform - Copy Equinox SDK from and include the following bundles into the base platform:
-
org.eclipse.equinox.servletbridge
-
org.eclipse.equinox.servletbridge.extensionbundle
-
org.eclipse.equinox.http.servletbridge
-
- Provide Servlet 3.0 API
- Copy
javax.servlet
3.0 from Orbit and include the bundles into the base platform
- Copy
- Provide the dependencies for Mockito
- Copy
org.objenesis
1.0 from Orbit and include the bundles into the base platform -
org.hancrest
should already be contained in the Eclipse Platform and thus there is no need to copy it
- Copy
- Copy
org.json
1.0.0 from Orbit into the base platform- The bundle can be found on build.eclipse.org using this path: /home/data/httpd/download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/repository/plugins
- We used to delete all junit4 bundles from the plugins folder, probably not needed anymore (?)
- Configure the hudson jobs to use the new base platform
- Build runtime and tooling
- Set parameter
BUILD_TYPE
toMx
for milestone builds,RCx
for release candidates, orR
for release builds - Set parameter
CVS_TAG
to the new tag (see above). DO NOT build milestones from HEAD
- Set parameter
- Copy a
notice.html
andepl-v10.html
into the root directory (eclipse) of the produced zip files (see bug 347659)
- Sign and upload files. This is currently done by the
publish.sh
script inorg.eclipse.rap.releng
Only for M1
- Update rap/latest-stable/{runtime/tooling} repositories to redirect to new repo
Publishing
- Finalize New & Noteworthy
- Update web site: new & noteworthy, downloads page, add links to previous version to archive page
- Scan Bugzilla for open bugs that are targeted at the milestone or bugs that are still open but solved, verify target version of closed bugs
- Notify the newsgroup
- Announce via Blog
- Re-deploy demo applications (in oder to demonstrate the new features from the milestone)
Procedure for release builds
additional steps to do when creating release builds
- ensure version numbers in bundle manifests
- ensure legal files (see [1])
- check that about.html are included in source build
- update infocenter content and links to infocenter from project home page
- update help plugin
- Check copyright year and version number of JavaDoc (search for "JavaDoc" in
org.eclipse.rap.releng/tooling/customTargets.xml
) - Move old builds to archive (
dev.eclipse.org:/home/data/httpd/archive.eclipse.org/rt/rap/downloads
), update archive page - Update the P2-repository URLs of install target action (see class o.e.r.ui.internal.intro.target.InstallTargetDialog)
- Update the RAP-tooling entry in the Eclipse Marketplace and in the Yoxos Marketplace. They should point to the latest release. (Beyhan)
- Redirect rap/latest-release/{runtime/tooling} repositories
- notify newsgroup and mailing list