PCM Development/Build Infrastructure/Upgrade of Eclipse Version

Add and release new target platform definition

• Add a new target platform definition to the Maven-Build-TargetPlatforms-Repository.
  • The list of features of the most recent eclipse version can be found here.
  • Add the new target platform as target file for the target-platform-validation-plugin in the pom of the repository in order for it to be verified automatically.
• Release a new version
  • Change version in the pom: Remove SNAPSHOT (<version>0.3.3-SNAPSHOT</version> --> <version>0.3.3</version>)
  • Merge to master so that the release is staged in Sonatype
  • Release in Sonatype (Staging Repositories -> Close -> Release)
• Set new development version
  • Increment version number and append -SNAPSHOT (<version>0.3.3</version> --> <version>0.3.4-SNAPSHOT</version>)
  • Merge to master so that the release is staged in Sonatype
  • Release in Sonatype (Staging Repositories -> Close -> Release)

Upgrading target platform definitions of individual projects

• Update references to eclipse repository locations
• Search in .XML, .target, .inf, .aggr und README.MD
  • http://download.eclipse.org/releases/>version</>subfolder</
  • http://download.eclipse.org/tools/orbit/downloads/>version</
  • http://download.eclipse.org/modeling/mdt/papyrus/updates/releases/>version</
  • https://download.eclipse.org/eclipse/updates/4.*/ (look here for fitting version number)
  • generally do a text search for each repository and replace the old version with new version if appropriate

• If possible: Change versions to 0.0.0 so the newest version in the repository is used
  • Exceptions:
    • Hamcrest
    • ...

• Update tycho-pomless version, if newer compatible version is available (Link)
  • .mvn/extensions.xml <artifactId>tycho-pomless</artifactId>
  • Possibly use version released before the new eclipse release to avoid errors.
    • For Eclipse 2021-09 use 2.4.0 released in Jul, 2021 and not 2.5.0 released Sep, 2021