Bug JRE version mismatch (UnsupportedClassVersionError) due to lack of independent JRE management

[swittlich]

When attempting to run the FSM/NetlistViewer tool, a "Verification Failed" crash occurs with an UnsupportedClassVersionError.

The error message states:

java.lang.UnsupportedClassVersionError: de/thkoeln/fentwums/fsm/Main has been compiled by a more recent version of the Java Runtime (class file version 65.0), this version of the Java Runtime only recognizes class file versions up to 61.0

• Class file version 65.0 corresponds to Java 21 (the version used to compile the backend binary).
• Class file version 61.0 corresponds to Java 17 (the version provided by the internal JRE package).

Currently, the only way a JRE is installed or provided in OneWare Studio is implicitly through the NetlistViewer plugin package. Because the plugin installs an outdated JRE (Java 17), it cannot execute the newer Java 21 binary, and there is no way for the user or system to update or supply a compatible JRE.

Proposed Solution

We need a way to decouple or update the JRE dependency to support newer binaries. This could be solved in a few ways:

• Short-term fix: Update the JRE dependency package in the NetlistViewer plugin to deploy JRE 21 (or newer) instead of JRE 17.
• Long-term architectural fix: Implement an independent, global JRE/JDK management system within OneWare Studio (similar to how Toolchains/Binaries are managed) so that plugins can dynamically point to a required minimum Java version or allow users to specify an external JRE path.