tree: 99e8ec19f50a3b13fb92885b543716d3559f886a [path history] [tgz]
  1. .project
  2. eclipse-capra-e4.10.target
  3. eclipse-capra-e4.10.tpd
  4. eclipse-capra-e4.11.target
  5. eclipse-capra-e4.11.tpd
  6. eclipse-capra-e4.12.target
  7. eclipse-capra-e4.12.tpd
  8. eclipse-capra-e4.13.target
  9. eclipse-capra-e4.13.tpd
  10. eclipse-capra-e4.14.target
  11. eclipse-capra-e4.14.tpd
  12. eclipse-capra-e4.15.target
  13. eclipse-capra-e4.15.tpd
  14. eclipse-capra-e4.16.target
  15. eclipse-capra-e4.16.tpd
  16. eclipse-capra-e4.6.target
  17. eclipse-capra-e4.6.tpd
  18. eclipse-capra-e4.7.target
  19. eclipse-capra-e4.7.tpd
  20. eclipse-capra-e4.8.target
  21. eclipse-capra-e4.8.tpd
  22. eclipse-capra-e4.9.target
  23. eclipse-capra-e4.9.tpd
  24. org.eclipse.capra.releng.target.target
  25. pom.xml
  26. readme.md
releng/org.eclipse.capra.releng.target/readme.md

Defining Target Platforms

We are using the TPD editor for target platforms which can be found at https://github.com/eclipse-cbi/targetplatform-dsl. 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 org.eclipse.capra.releng.target.target 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

  • Neon.tpd - original platform for which Capra was developed
  • Oxygen.tpd
  • 2018-09.tpd - latest build platform