Closed jjfumero closed 5 months ago
Lets remove it as we have support with the latest LTS(21).
Also, as we add support for JDK22 which does not have backwards compatiblity due to graalvm paths change, we will end up maintaining 3 different jdks version (17, 21, 22).
I agree, then lets remove it.
I agree lets remove it for the aforementioned reasons.
OK, I am deleting the branch.
Is your feature request related to a problem? Please describe.
Since TornadoVM moved to OpenJDK 21 with Panama Memory API, there is a compatibility issue with JDK 17. Thus, for known use cases using JDK17, TornadoVM had the option to run with jdk17 without the Panama integration. However, all known uses cases for TornadoVM as well as running projects (e.g., AERO), are running with JDK21+, so there is no need to maintain the old one.
Besides, with JDK22, the JVMCI/GraalVM integration has also changed, which means that TornadoVM will have a new branch as well for JDK22+ changes.
Describe the solution you'd like
I suggest removing the JDK 17 branch and focus to 21 as minimum from now on.
Describe alternatives you've considered
n/a.
Additional context n/a.