OML tools v2.13+ require Java 21

[melaasar]

Dear community,

Some of OML's dependencies have moved to Java 21 requiring us to upgrade OML release v2.13 to Java 21.

How does this impact you?

If your OML projects use a dynamic version 2.+ for OML related tools (any tool with oml in its name), the next time you use them, it will pick up v2.13.0, which requires Java 21. This means if the Java currently in your environment is less than 21, you will be getting some problems running the OML tools (mostly complaints about java major versions).

The fix is either to hard-code your OML dependencies to v2.12.+ (this will pin your project to that minor version), or alternatively (recommended) you upgrade the Java in your environment to 21.

Notice that If you use OML Rosetta, then upgrading it to v2.13.0 will come with Java 21 bundled-in already. However, if you invoke the gradle tools through Terminal, then you need to make sure the Java version in that environment is 21+.

• If you upgraded to Java 21+ in your environment, then the version of Gradle Wrapper (i.e., gradlew) used by your project needs to also be upgraded to v8.5 or higher (as per Gradle docs).

You can do this by either editing gradle/wrappaer/gradle-wrapper.properties file and replacing the existing version, for example distributionUrl=https\://services.gradle.org/distributions/gradle-8.10-bin.zip, or alternatively you can achieve the same result by running in Terminal the command ./gradlew wrapper --gradle-version 8.10.

• If you upgraded Java and Gradle Wrapper as suggested above, and if you use CI/D scripts in your git repository, then also remember to change the required Java version in those scripts to 21+.

If you have a question on this change, please post as replies to this thread. Thanks.