Thanks Michael, I figured it was something like this. For my own
projects I have the freedom to stay more or less up-to-date on release
versions (although typically target LTS), so I've encountered such
ASM/Groovy issues myself between NB/Gradle/Java versions when trying to
stay bleeding-edge. Nevertheless I thought I'd add the comment in case
was intended to build on JDK21, and my specific platform config happened
to throw the clog in the loom.
Anyhow, as already stated, happy with my +ve vote, and now already using
that version of NB for dev :)
Stan
On 29/11/2023 13:09, Michael Bien wrote:
Hi Giles,
(to take the discussion of the voting thread)
I'm uncertain if the intention is for it to build on JDK21, but when
I tried (Adoptium OpenJDK 21) it failed (Groovy/ASM issue):
gradle depends on groovy which depends on ASM and at least one module
uses gradle during the build, see readme:
https://github.com/apache/netbeans?tab=readme-ov-file#notes-1
or
https://github.com/apache/netbeans/issues/6125
gradle is typically lacking 1-2 JDK releases behind in terms of java
runtime of the daemon, workaround is to run the gradle daemon on an
older JDK and the build should run fine using JDK 21, more details in
the links above or the github actions yaml.
(release build builds on JDK 11)
best regards,
michael
---------------------------------------------------------------------
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
