@@ -98,6 +98,7 @@ This requires giving the unmanaged profile the name _tmp_ again, as before.
...
@@ -98,6 +98,7 @@ This requires giving the unmanaged profile the name _tmp_ again, as before.
*** Commit the preference changes.
*** Commit the preference changes.
*** Reformat all projects.
*** Reformat all projects.
*** Commit reformatting changes.
*** Commit reformatting changes.
** If any changes were made to the formatter preferences, manually update the `org.eclipse.escet.*.metamodel` projects to have the same formatter settings as the rest of the projects.
* Java errors/warnings settings
* Java errors/warnings settings
** Right click the `org.eclipse.escet.common.java` project in the _Package Explorer_ view and choose menu:Properties[].
** Right click the `org.eclipse.escet.common.java` project in the _Package Explorer_ view and choose menu:Properties[].
...
@@ -165,25 +166,29 @@ Upgrading Java may require upgrading Eclipse to a newer version that supports th
...
@@ -165,25 +166,29 @@ Upgrading Java may require upgrading Eclipse to a newer version that supports th
To upgrade to a new Java version:
To upgrade to a new Java version:
* For major Java versions (e.g. 17 to 18):
* For major Java versions (e.g. 17 to 18):
** Update `Bundle-RequiredExecutionEnvironment` for all plug-in manifests.
** Update all (plugin) projects:
** Update `JRE_CONTAINER` in all `.classpath` files.
*** Update `Bundle-RequiredExecutionEnvironment` for all plug-in manifests.
** Update `JRE_CONTAINER` in all launch configurations (`.launch` files).
*** Update `JRE_CONTAINER` in all `.classpath` files.
** Update Java versions in `org.eclipse.jdt.core.prefs` files (`compiler.codegen.targetPlatform`, `compiler.compliance`, and `compiler.source`).
*** Update `JRE_CONTAINER` in all launch configurations (`.launch` files).
** Update `autofix.py` by changing the replaced by compliance level and adding new compliance levels to change (`org.eclipse.escet.chi.metamodel`, `org.eclipse.escet.cif.metamodel`, `org.eclipse.escet.common.position.metamodel`, and `org.eclipse.escet.tooldef.metamodel`).
*** Update Java versions in all `org.eclipse.jdt.core.prefs` files (`compiler.codegen.targetPlatform`, `compiler.compliance`, and `compiler.source`).
** Run the `autofix.py` script.
** Update all metamodel projects (`org.eclipse.escet.*.metamodel` projects):
Changes should be observed in `chi.genmodel`, `cif.genmodel`, `position.genmodel`, and `tooldef.genmodel`.
*** Update the `autofix.py` scripts of these projects, by changing the compliance level resulting from replacements.
** Regenerate model code by opening the `.genmodel` files and right click and choose menu:Generate Model Code[].
*** Change in all `*.genmodel` files the `complianceLevel`.
*** Regenerate the model code for each metamodel project, by opening the corresponding `.genmodel` file, right clicking the root node of the opened generator model, and choosing menu:Generate Model Code[].
There won't always be changes.
There won't always be changes.
** Update `osgi.requiredJavaVersion` in the product (`org.eclipse.escet.product/escet.product`).
** Update the product:
** Update `osgi.requiredJavaVersion` in the product launch configuration (`org.eclipse.escet.product/product-escet.launch`).
*** Update `osgi.requiredJavaVersion` in the product (`org.eclipse.escet.product/escet.product`).
** Update Java version for `escet.java.version` in `org.eclipse.escet.releng.configuration/pom.xml`.
*** Update `osgi.requiredJavaVersion` in the product launch configuration (`org.eclipse.escet.product/product-escet.launch`).
** Update Java version for `executionEnvironment` in `org.eclipse.escet.releng.configuration/pom.xml`.
** Update the build:
** Update Java version in `Jenkinsfile`.
*** Update Java version for `escet.java.version` in `org.eclipse.escet.releng.configuration/pom.xml`.
** Update Java version in `misc/license-check-dependencies/Jenkinsfile`.
*** Update Java version for `executionEnvironment` in `org.eclipse.escet.releng.configuration/pom.xml`.
** Update Java keywords for `org.eclipse.escet.common.java.JavaCodeUtils.JAVA_IDS`.
*** Update Java version in `Jenkinsfile`.
*** Update Java version in `misc/license-check-dependencies/Jenkinsfile`.
** Update all Java code and documentation:
*** Update Java keywords for `org.eclipse.escet.common.java.JavaCodeUtils.JAVA_IDS`.
Update the keywords themselves and the field's JavaDoc, including the link to the Java Language Specification (JLS).
Update the keywords themselves and the field's JavaDoc, including the link to the Java Language Specification (JLS).
** Update `dev-env-setup.asciidoc` to match new Java version.
*** Update `dev-env-setup.asciidoc` to match new Java version.
** Update documentation links to the new version (search for `https://docs.oracle.com`).
*** Update links to specific versions of the Java documentation (search for `https://docs.oracle.com`).
** Search for the current Java version to find other references (e.g., search for `17`).
** Search for the current Java version to find other references (e.g., search for `17`).
* For any Java versions (e.g. 17 to 18, or 17.0.1 to 17.0.2):
* For any Java versions (e.g. 17 to 18, or 17.0.1 to 17.0.2):
