Skip to main content
Jump to: navigation, search

EASE/TargetUpdate

< EASE
Revision as of 04:01, 8 July 2020 by Christian.pontesegger.web.de (Talk | contribs) (Created page with "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: * [https://bugs.eclipse.org/bugs/en...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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. Once working, merge the changes to the master branch.

Update Jenkins verification builds

Back to the top