The GitHub Actions job "JMH Benchmark Comparison" on grails-core.git/feat/indy-default-groovy6 has succeeded. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: 38fd73b5dee9dfb4ccbfb81deeb3ddb08f54297c / James Daugherty <[email protected]> Make the applications the Forge specs generate declare groovy-callsite in the classic lane The two Forge builds that run with -PgrailsIndy=false failed in the specs that generate an application and build it. The property reaches the included grails-core build, so the framework those applications consume from build/local-maven is compiled with classic call sites, which Groovy 6 loads only with groovy-callsite; the generated application, compiled with invokedynamic and without the module, could not load the @Integration transform or the JSON view compiler. Until the module left grails-common every application got it transitively. A real application never meets a classic-compiled Grails, since a published one is compiled with invokedynamic, so the generated build files stay as Forge writes them. Instead, in that lane, the Forge build names an init script in a system property of the test tasks that build generated applications, and both harnesses run every generated build with it. The script declares the module on every source set of the generated project, as any application that depends on a library compiled that way must. GeneratedBuild in the CLI module's test fixtures turns the property into the arguments, and GeneratedBuildSpec covers it. Report URL: https://github.com/apache/grails-core/actions/runs/38823598029 With regards, GitHub Actions via GitBox
