Tracing code fails as of Java19

[TimLethbridge]

(see comments at the end ... this issue has to wait for several years ... a partial workaround was done in Feb 2023 through PR #2022)

Tests of Umple tracing code are failing as of Java 19, due to deprecations.

We need to make changes such that tracing works from Java 11 onwards (or at least Java 17 onwards)

The examples that fail from the build are:

[java]  /Users/tcl/unix/umple/temp/java/Tracers1.ump
 [java]  /Users/tcl/unix/umple/temp/java/Tracers2.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingAssociations1.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingAssociations2.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingAssociations3.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingAttributes1.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingAttributes2.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingAttributes3.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingAttributeswithConditions2.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingAttributeswithOccurrences1.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingAttributeswithOccurrences2.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingAttributeswithtimeline1.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingAttributeswithtimeline2.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingBasics1.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingBasics2.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingConstraints1.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingConstraints2.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingConstraints3.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingMethods1.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingMethods2.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingStateMachines1.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingStateMachines2.ump
 [java]  /Users/tcl/unix/umple/temp/java/TracingStateMachines3.ump
 [java]  /Users/tcl/unix/umple/temp/java/W301TracingEntityNotFound2.ump __UMPLEc3RyaWN0bmVzcyBpZ25vcmUgMzAxOw==
 [java]  /Users/tcl/unix/umple/temp/java/W302TracerNotRecognized1.ump __UMPLEc3RyaWN0bmVzcyBpZ25vcmUgMzAyOw==
 [java]  /Users/tcl/unix/umple/temp/java/W302TracerNotRecognized2.ump __UMPLEc3RyaWN0bmVzcyBpZ25vcmUgMzAyOw==

[TimLethbridge]

This page says that getId is replaced by threadId in Java 19 so the change should be not hard.

See
https://bugs.openjdk.org/browse/JDK-8017617?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel

The Umple code that uses thread getID is at cruise.umple/src/generators/Generator_CodeJava.ump line 3382 where it says

TraceLookupMap.put("thread","Thread.currentThread().getId()");

The only catch is that we need to know when this change will take over as it will restrict the applicability of generated code. If we roll it out it will force users to use Java 19

Java 19 doc is here
https://docs.oracle.com/en/java/javase/19/docs/api/java.base/java/lang/Thread.html

As of the time of this issue Umple supports Long term stable versions 11 and 17

Possiblity A for interim solution is to add @SuppressWarnings("deprecation") to the methods that use Thread.getId. THen wait until Java 21 comes out in Fall 2025 (the next long term support release) and some time after that make the API change and require use of Java 19 to 25 (with either stable version 21 or stable version 25.

The challenge with that is ensuring the correct various generated methods that use tracing have the deprecation annotation added before them ... and then changing all the tests.

Possibility B is to fix the test code so it doesn't fail when run in Java 19.

[TimLethbridge]

This pull request is being left open until likely 2025, when the cruise.umple/src/generators/Generator_CodeJava.ump can be changed to use the new API, at which time Java19 would be the lowest version that could be used.