Update to Eclipse 2018-12 & JDK-11
The oracle JDK 1.8 (public version) is no longer maintained from the end of January. Hence, we need to switch to JDK-11 since the versions 9 and 10 are already no longer maintained. Due to the refactoring of the SDK, we now have to include OpenJFX that is missing from the SDK now. Furthermore, we need to update to version 2018-12 from Photon to obtain proper JDK-11 support.
This task includes:
- Updating the developer installation.
- Including OpenJFX (dependencies) in the oomph installation and maven.
- Fix incompatibility issues due to JDK-11.
- Update the Jenkins (maven-based) build.
#1 Updated by Alexander Diewald over 1 year ago
- % Done changed from 0 to 50
- The AF3 code compiles.
- All plugins require JavaSE-11 now: This change is needed to include the JDK as a modular library that in turn is required to support JavaFX/efxclipse.
- The Oomph setup is adjusted to automatically download the OpenJFX SDK to the eclipse installation and reference it for the efxclipse IDE plugins.
- The Oomph setup is updated to install eclipse 2018-12 that properly supports JDK-11.
- We now use a target definition as advised by eclipse itself and the author of efxclipse.
- The oomph setup was pruned to only contain the p2 repos that are relevant for the Developer IDE: All runtime plugins are defined in the target definition such as SWTBot.
- The AF3 RCP starts up.
Despite the RCP starting up there is a performance issue leading to extremely long delays in startup (5-10 mins) and usage (some actions take >10mins). This is due to a pseudo-endless loop documented in this issue: https://github.com/eclipse-efx/efxclipse-rt/issues/292
We may expect this problem to be fixed soon :)
The corresponding setup file is to be found in the 3620 branch of fortiss-std-env. It points to corresponding branches in each used repo.
#3 Updated by Alexander Diewald over 1 year ago
- Status changed from New to In Progress
- % Done changed from 60 to 90
The maven setup is basically done, and jenkins jobs are already created.We will use a single maven-releng repo for:
- local builds,
- jenkins builds,
- derived builds (local or jenkins).
This step will enable us to use a single configuration for the AF3 product (unification).
Despite efxclipse not yet being released, we should probably update before its release date (28th of February) such that we have a chance to discover hidden bugs before the release.
The switch should definitely been done with this release since we would force users in companies that do not have a paid Oracle license to use an insecure java version for 6 more months.
- Cleaning af3-dev-product.
- Merge 3620.
- Adjusting the rollout jenkins job.
- Write to the mailing list about the required reinstallation.
- Update the docs.
- Document the maven setup.