tree: 21992361feb166d1e09ac2ffedc3551d4d80272b [path history] [tgz]
  1. .project
  3. eclipse-capra-e4.19.tpd
  5. eclipse-capra-e4.20.tpd
  7. eclipse-capra-e4.21.tpd
  9. eclipse-capra-e4.22.tpd
  11. eclipse-capra-e4.23.tpd
  13. eclipse-capra-e4.24.tpd
  15. pom.xml

Defining Target Platforms

We are using the TPD editor for target platforms which can be found at It currently only works in Eclipse versions >= 2018.09, but can generate target definitions for any Eclipse platform.

It allows defining target definitions with a DSL and generating .target files from them automatically. During the generation, the latest versions of the selected features are selected and added to the definitions.

We are following a scheme that is used by some other Eclipse projects, e.g., EASE.

Building and developing

Tycho will use the file for builds. This file has to be manually overridden when a new target platform has been created.

When developing, any of the target platforms can be used by first generating a target definition and then setting it as the current target platform. This allows developers to check compatibility in different Eclipse versions.

Available targets

There are target platform files available for each Eclipse version starting from Eclipse Neon. Each target platform will draw from the corresponding repositories for the Eclipse platform and Eclipse Orbit.