Skip to main content
Jump to: navigation, search

EASE/TargetUpdate

When a new Eclipse version is released, we need to update the target platform, setup and the web page. Following steps need to to be done:

Update target platform

  • copy the current target files (org.eclipse.ease.releng.target.*) from org.eclipse.ease.releng.target to the previous targets subfolder. Rename the copied targets accordingly to reflect their eclipse version.
  • update org.eclipse.ease.releng.target.tpd to the newest eclipse version. Typically this means to update the target name, the download.eclipse.org location and the orbit location.
  • save the tpd file and create the target file from it.
  • update org.eclipse.ease.modules.releng.target.tpd to the newest eclipse version. Save and create the target file from it

Update Oomph setup

Apply following changes to the Oomph setup file:

  • Add a new repository list item to EASE/Core Framework/Modular Target/${scope.project.label}. Best copy the previous one and adapt the download locations.
  • Change EASE/Core Framework/eclipse.target.platform to reflect the newly created target
  • Apply the same two changes to the Modules Development node


Now commit all changes using the bug entry you created in the beginning. Cross your fingers that the gerrit builds work. In case they break, we need to manually review the target platform for changed/missing/broken dependencies and fix them. Most errors are caused by new bundle versions with a higher version number. This can easily be fixed by updating the affected manifest files.

Once working, merge the changes to the master branch.

Update Jenkins verification builds

  • Create a new Jenkins job to verify the previous target definition. So if you upgraded from 2020-03 to 2020-06, create a job ease.verify.core.target.2020-03. Use one of the other ease.verify.core.target.* jobs as a template.
  • In its pipeline definition, there is a Test step. Make sure to copy the correct target from the previous targets folder.

Update webpage

  • update the download site and add a new row to the compatibility matrix. Make sure to reference the jenkins verify job just created before.

Back to the top