Hi all, a recent update to the JDK (released in JDK 22) broke GraalJS in NetBeans:
https://github.com/apache/netbeans/issues/7245 I tried to update GraalJS for the last three days and at the end I noticed, that the version I was working with broke less obviously, than the old one. So it was useless. I was working with 23.0.3 because after that graalvm changed packaging. Turns out, I should have looked closer. So where to go from here? The dependencies suggested by GraalVM pull in: +- org.graalvm.polyglot:polyglot:jar:24.0.0:compile | +- org.graalvm.sdk:collections:jar:24.0.0:compile | \- org.graalvm.sdk:nativeimage:jar:24.0.0:compile | \- org.graalvm.sdk:word:jar:24.0.0:compile \- org.graalvm.polyglot:js-community:pom:24.0.0:compile +- org.graalvm.js:js-language:jar:24.0.0:runtime | +- org.graalvm.regex:regex:jar:24.0.0:runtime | +- org.graalvm.truffle:truffle-api:jar:24.0.0:runtime | \- org.graalvm.shadowed:icu4j:jar:24.0.0:runtime \- org.graalvm.truffle:truffle-runtime:jar:24.0.0:runtime +- org.graalvm.sdk:jniutils:jar:24.0.0:runtime \- org.graalvm.truffle:truffle-compiler:jar:24.0.0:runtime So we need to rethink the packaging in NetBeans. I see as options: - rip out everything that looks like GraalVM and Truffle and replace it with a single module that only wraps GraalJS - remap the current modules to the new GraalVM structure - drop everything Graal and switch back to rhino I'm a bit fed up about this. The Graal looks a bit less shiny now and the old rhino looks much nicer. The question: How complex are pac Scripts in reality? Is dropping Graal an option? Greetings Matthias --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
