I think you are hitting a series of "edge" cases. I put the edge in quotes as, most probably, they shouldn't be.
1. I've seen the CRC32C exception in Gradle from time to time, especially when dealing with modular applications. 2. Yes it's true Java Toolchain is not fully supported in NB17, the bootclasspath would be always the Gradle Runtime boot CP 3. Due to these, or totally independently the Javac let you down with an NPE Again a minimal reproducible project would be good, but this is a nasty one. On Mon, Jan 30, 2023 at 7:11 AM Scott Palmer <swpal...@gmail.com> wrote: > Yes.. well maybe... > For that project the source level is set to 17, but the Java Runtime for > Gradle execution is set to JDK 19. The build.gradle file uses the > toolchain mechanism to specify JDK 17. The JDK 19 reference is likely left > over from some experiments. They are all valid JDK folders, but I thought > maybe the mix of 17 & 19 was causing NB some confusion, so I changed it to > JDK 17 (default) and even restarted NB, but the problem remains. > NetBeans is running with netbeans_jdkhome set to 17 in the netbeans.conf > file. > > Scott > > On Mon, Jan 30, 2023 at 8:37 AM Neil C Smith <neilcsm...@apache.org> > wrote: > > > On Mon, 30 Jan 2023 at 00:16, Scott Palmer <swpal...@gmail.com> wrote: > > > More failures to rename... > > > ... > > > Even though the source level of ... is set to: 17, java.util.zip.CRC32C > > cannot be found on the system module > > > path: > > > > That seems suspicious. Are you sure the jdkhome for the IDE and any > > per-project platform are correctly configured? > > > > Neil > > > > --------------------------------------------------------------------- > > 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 > > > > > > > > >
