Jump to: navigation, search

ETrice/Development/PlatformSwitch

Switch of the Eclipse Platform

Recently we developed eTrice on the base of the Juno platform. Now we switched to Kepler.

There are a couple of things that should be carefully done and checked to make the transition as smooth as possible:

all developers

  • download the modeling package of the new platform
  • install
    • Xtext
    • Xtend
    • Graphiti
    • Guava (from Orbit) and Guava 8.0 from Google (needed by KIELER)
    • KIELER
    • Buckminter (only as editor for resource maps and component specifications)
  • let ETRICE_TARGET_PLATFORM point to the new platform
  • adjust the workspace settings for the compiler to 1.6
  • choose a default 1.6 JRE (or even better a JDK)

has to be done once only and committed and pushed

  • adjust the class path version numbers of
    • /org.eclipse.etrice.runtime.c.tests/make.xml, target convert
    • /org.eclipse.etrice.generator.java.tests/make.xml, targets generate and convert
    • /org.eclipse.etrice.generator.c.tests/make.xml, targets generate and convert
  • adjust the Buckminster resource map /org.eclipse.etrice.releng/build.rmap to the new platform
  • push to Hudson and test the build

Hrr.protos.de 08:37, 2 July 2013 (UTC)