The GitHub Actions job "Groovy Snapshot Canary Build" on grails-core.git/feat/indy-default-groovy6 has failed. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: 17d694d3af25c224bfc4c13855761d8c343a1a64 / James Daugherty <[email protected]> Ship groovy-callsite only when an application opts out of invokedynamic grails-common declared org.apache.groovy:groovy-callsite as an api dependency, so every Grails 9 application carried the module whether or not it compiled classic call sites, which Grails 9 does not by default. The dependency is gone: an application that sets grails { indy = false } declares the module itself, at the version the Grails BOM manages, and the Groovy compiler names it when it is missing. What's New, the 9.0 upgrade guide and the extension's javadoc say so. CI's -PgrailsIndy=false lane compiles every source set of the Grails plugin modules and example apps with classic call sites, so the shared grails-extension-gradle-config script, which applies that flag, now declares the module for each source set of such a project. The version is read from the map in dependencies.gradle, applied to the root project once in that lane as the build-logic builds apply it, because the ast source set the Grails plugin gives every plugin project has no platform on its configurations to supply one. The Forge CLI test fixtures no longer need their own declaration: they compile with invokedynamic like everything else. The TestKit fixtures' Groovy sources that the previous commit's bytecode and late-override features compile were left out of it; they are added. Report URL: https://github.com/apache/grails-core/actions/runs/38662366397 With regards, GitHub Actions via GitBox
