Re: m-compiler-p + groovy-eclipse-compiler + spock and groovy with CL
To close this thread, I want to mention that the problem is not in Maven or Spock, but I identified it in the Groovy Eclipse Batch Compiler. See https://github.com/groovy/groovy-eclipse/issues/1648. -- Alexander Kriegisch https://scrum-master.de Piotr Żygieło schrieb am 14.12.2025 um 15:48: > On Sun, 14 Dec 2025 at 06:46, Alexander Kriegisch > wrote: >> I have not used Spock in a while, but just fired up my sample project, >> also using GrEclipse. > > Thanks for checking. > >> I can confirm the problem, but noticed that until >> 2.4-M6-groovy-4.0, compilation works. It starts breaking with the error >> you observed in your sample project since 2.4-M7-groovy-4.0. >> Maybe, it >> is worth discussing this with the Spock people. > > That's what I've observed as well as described and discussed in > https://github.com/spockframework/spock/issues/2282. - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Re: m-compiler-p + groovy-eclipse-compiler + spock and groovy with CL
On Sun, 14 Dec 2025 at 06:46, Alexander Kriegisch wrote: > I have not used Spock in a while, but just fired up my sample project, > also using GrEclipse. Thanks for checking. > I can confirm the problem, but noticed that until > 2.4-M6-groovy-4.0, compilation works. It starts breaking with the error > you observed in your sample project since 2.4-M7-groovy-4.0. > Maybe, it > is worth discussing this with the Spock people. That's what I've observed as well as described and discussed in https://github.com/spockframework/spock/issues/2282. Piotrek - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Re: m-compiler-p + groovy-eclipse-compiler + spock and groovy with CL
Hi Piotr. I have not used Spock in a while, but just fired up my sample project, also using GrEclipse. I can confirm the problem, but noticed that until 2.4-M6-groovy-4.0, compilation works. It starts breaking with the error you observed in your sample project since 2.4-M7-groovy-4.0. Maybe, it is worth discussing this with the Spock people. What changed in Spock Core or the Spock BOM between those two milestones, and how does it influence compilation results? Locally, I used: Maven Compiler 3.8.1 Groovy 4.0.29 Spock >= 2.4-M7-groovy-4.0 to reproduce the problem, lower to be fine GrEclipse Compiler 3.9.1 GrEclipse Batch 4.0.29-01 If you open a discussion or issue in the Spock project, feel free to mention me (@kriegaex). Thanks. Best regards -- Alexander Kriegisch https://scrum-master.de Piotr Żygieło schrieb am 14.12.2025 um 05:02: > Hello Maven Community > > I'm facing issue [1] where after upgrading SpockFramework from 2.3 to > 2.4 the compilation (maven 3.9.11, m-compiler-p:3.14.1, groovy: > 4.0.29) fails with: > > Groovy:General error during canonicalization: > Transform org.spockframework.compiler.SpockTransform cannot be run > > due to Groovy's ReleaseInfo not being populated from resource [2] and > it returns an empty string instead of the real version in [3]. And > (new) Spock 2.4 wants to know that version. > > I'm not sure how classworlds work, and why during plugin execution the > Groovy's resource is not available (while regular o.c.groovy classes > are loaded fine), thus I'm not sure where this could/should be > adjusted - in maven-compiler-plugin or in > groovy-eclipse-compiler/groovy-eclipse-batch or if this is somehow > solvable in the final project. > > Maybe the reproducer [4] could show it much better than I try to > describe it here. > > Regards, > > Piotrek > > 1. https://github.com/spockframework/spock/issues/2282 > 2. > https://github.com/apache/groovy/blob/f1c3f38aa3c1c31bdfd0ee7bf2c3e1d8c36a9437/src/main/java/org/codehaus/groovy/util/ReleaseInfo.java#L46 > 3. > https://github.com/apache/groovy/blob/f1c3f38aa3c1c31bdfd0ee7bf2c3e1d8c36a9437/src/main/java/org/codehaus/groovy/util/ReleaseInfo.java#L67 > 4. https://github.com/pzrep/spock-2.4-canonicalization/pull/2 > > - > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
m-compiler-p + groovy-eclipse-compiler + spock and groovy with CL
Hello Maven Community I'm facing issue [1] where after upgrading SpockFramework from 2.3 to 2.4 the compilation (maven 3.9.11, m-compiler-p:3.14.1, groovy: 4.0.29) fails with: Groovy:General error during canonicalization: Transform org.spockframework.compiler.SpockTransform cannot be run due to Groovy's ReleaseInfo not being populated from resource [2] and it returns an empty string instead of the real version in [3]. And (new) Spock 2.4 wants to know that version. I'm not sure how classworlds work, and why during plugin execution the Groovy's resource is not available (while regular o.c.groovy classes are loaded fine), thus I'm not sure where this could/should be adjusted - in maven-compiler-plugin or in groovy-eclipse-compiler/groovy-eclipse-batch or if this is somehow solvable in the final project. Maybe the reproducer [4] could show it much better than I try to describe it here. Regards, Piotrek 1. https://github.com/spockframework/spock/issues/2282 2. https://github.com/apache/groovy/blob/f1c3f38aa3c1c31bdfd0ee7bf2c3e1d8c36a9437/src/main/java/org/codehaus/groovy/util/ReleaseInfo.java#L46 3. https://github.com/apache/groovy/blob/f1c3f38aa3c1c31bdfd0ee7bf2c3e1d8c36a9437/src/main/java/org/codehaus/groovy/util/ReleaseInfo.java#L67 4. https://github.com/pzrep/spock-2.4-canonicalization/pull/2 - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
