Fix/temurin

[akurtakov]

What it does

Switches Jenkins build JVM to Temurin so latest 17.x version is used.

How to test

Build still works

Author checklist

• I have thoroughly tested my changes
• The change is following the coding conventions
• I have signed the Eclipse Contributor Agreement (ECA)

[iloveeclipse]

Switches Jenkins build JVM to Temurin so latest 17.x version is used.

Do we have problems with "old" Java 17 versions? If yes, which? If no, why should we change?

[akurtakov]

Most notable reason to use 17.0.5 is https://bugs.openjdk.org/browse/JDK-8269039 which made some jars appear as unsigned late in the 4.27 cycle.

But even ignoring that using latest bugfix release should be the norm as these bugfix releases are what end users end up with (JustJ https://download.eclipse.org/justj/jres/17/downloads/latest/ in EPPs) so it's best to run verification with same bugfix level.

[iloveeclipse]

Do you plan / do we need to change this overall in the platform / JDT / PDE / equinox too?

[akurtakov]

Do you plan / do we need to change this overall in the platform / JDT / PDE / equinox too?

Majority are already handled. git submodule foreach "git grep openjdk-jdk17-latest;true"|grep Jenkins gives 7 Jenkinsfiles. In general I handle them as I come to a repo for some reason but I would very welcome if someone wants to speed it up.

[iloveeclipse]

Alex, if you have the list at hand, please post here, I will check that in context of eclipse-jdt/eclipse.jdt.core#883 & eclipse-jdt/eclipse.jdt.ui#493

[akurtakov]

'eclipse.jdt' -> Jenkinsfile: jdk 'openjdk-jdk17-latest'
'eclipse.jdt.debug' -> Jenkinsfile: jdk 'openjdk-jdk17-latest' Done by this patch
'eclipse.jdt.ui' -> Jenkinsfile: jdk 'openjdk-jdk17-latest'
'eclipse.platform' -> Jenkinsfile: jdk 'openjdk-jdk17-latest'
'eclipse.platform.swt' -> Jenkinsfile: jdk 'openjdk-jdk17-latest'
'eclipse.platform.swt.binaries' Jenkinsfile: withEnv(["JAVA_HOME=${ tool 'openjdk-jdk17-latest' }"]) {
'rt.equinox.p2' Jenkinsfile: jdk 'openjdk-jdk17-latest' Being worked on