Le dim. 14 avr. 2024 à 17:44, MG <mg...@arscreat.com> a écrit : > > Just a long shot, but have you checked if this error might be due to a > broken build or similar, i.e. class files being modified in parallel or > source files having been modified while the build process was running ?
I limit the number of spanning processes to 6 during gradle build, and the issue looks systematic. If this is the issue, I will open a bug report. I will restrict to 1 concurrent process during build to test. > We see "ArrayIndexOutOfBoundsException: size==0" exceptions from time to > time during IntelliJ Groovy builds, and the cause is typically as stated > above. Building anew (sometimes rebuilding a module or the whole project > is required) typically fixes these... (we had some which were actual > bugs in the Groovy compiler, but these are very rare). I removed '.gradle' from 'buildSrc' and from my home. No changes... > On 14/04/2024 15:54, Adrien Guichard wrote: > > Le dim. 14 avr. 2024 à 12:18, Paul King <pa...@asert.com.au> a écrit : > >> Can you give us more of the stack trace where Groovy is failing for > >> the "size==0" error? > > java.lang.ArrayIndexOutOfBoundsException: size==0 > > at > > org.codehaus.groovy.classgen.asm.OperandStack.ensureStackNotEmpty(OperandStack.java:279) > > at > > org.codehaus.groovy.classgen.asm.OperandStack.replace(OperandStack.java:271) [. . .] > > > >> I would in general expect very few changes needed between 3 and 4. > > I was wrong, Grails 6.2.0 is Groovy 3.0.21 (from 3.0.11) -- Adrien Guichard + 33 6 10 78 75 88 https://taack.org 29 Boulevard Edgar Quinet 75014 Paris
