Ok I suspected that is the answer. I can stay on 30 for now, since we are heavily lombok based and they are not ready for jdk27.
Maybe there should be a big migration notice on the Netbeans Download page stating that Lombok is currently not supported in NB31? So it jumps out at developers? I’m sure I’m not the only one who will run into this. > On Aug 11, 2026, at 4:18 PM, Michael Bien <[email protected]> wrote: > > On 8/11/26 21:06, Tim Mullé wrote: >> Just tried to use 31 on a very large project which works fine under 30 and >> lombok 1.18.38. >> >> Just changing the Netbeans IDE from 30 to 31 causes the javac/lombok >> collisions because I think the `nb-javac` is running against jdk 27? and >> lombok does’t support that yet so the code editor gives lots of warnings on >> any Lombok annotated classes. >> >> Compiling from the command line still works as usual. >> >> Is there a fix for 31? I had to revert back to 30 for now. > > the fix would be lombok adding support for JDK 27. > > The NetBeans 31 editor uses javac of JDK 27 for language support. > > NB 30 used the javac of JDK 26. Odd NB versions update the javac. > > regards, > > michael > > >> >> Thanks! >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> For further information about the NetBeans mailing lists, visit: >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
