Author: ince
Publication Date: 1/11/2021 14:16
*** relevant for Cloud Customers & Partner only ***
Dear Customer & Partner,
As you already know, we started to migrate FirstSpirit™ from Java 8 to Java 11 in November.
What do I have to do?
Unlike our modules, which have already been tested for Java 11, the compatibility of "custom modules" (modules not provided by e-Spirit) is not necessarily guaranteed. Therefore, they have to be checked and, if necessary, adapted to the functionality of Java 11. Please contact the developer of the module for this. If he is not available, our Professional Service and our implementation partners will be happy to provide support.
Attention: The bytecode of the module must not be Java 11, it only has to be Java 11 compatible!
Just keep your Java compiler settings as before to create Java 8 bytecode.
Example: Gradle, groovy
sourceCompatibility = JavaVersion.VERSION_1_8
targetCompatibility = JavaVersion.VERSION_1_8
Within your cloud ci infrastructure (Bamboo) all artifacts (e.g. FirstSpirit Modules) will still be compiled with Java 8 to ensure that Java 8 bytecode will be created.
What is the schedule? When do I have to finish the adjustments?
The changeover to Java 11 takes place in three steps. Starting with the November Patch Day, the FirstSpirit™ cloud instances will be converted. Until the February Patch Day we offer the rollback to Java 8 via an opt-out possibility.
| Date | What | Note |
| November Patch Day 18.11.2020 | Instance Development (DEV) is upgraded. | OPT-OUT (Rollback to Java 8 possible) STATUS: UPGRADE DONE! |
| January Patch Day 20.01.2021 & 27.01.2021 | Instances Quality Assurance and Production (QA & PROD) will be upgraded. Bytecode-Level must not be Java 11! | OPT-OUT (Rollback to Java 8 possible) |
| February Patch Day 17.02.2020 & 24.02.2020 | No further rollback to Java 8 possible. Java 11 is default. | OPT-IN |
If you have any questions, please feel free to comment.
Kommentare
0 Kommentare
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.