You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@grails.apache.org by GitBox <gi...@apache.org> on 2026/10/14 21:10:38 UTC
[GH] (grails-core/feat/indy-default-groovy6): Workflow run "CI" failed!
The GitHub Actions job "CI" on grails-core.git/feat/indy-default-groovy6 has failed.
Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run:
d71024dd8b31c65d4bb1cc4465bedeeb90dc0059 / James Daugherty <jd...@jdresources.net>
Leave indy at the Groovy compiler's default unless the application sets it
Gradle passes no indy option to the Groovy compiler unless a build sets
one, and the compiler then uses its own default, which is invokedynamic
on Groovy 5 and 6. Grails 7 and 8 have to override that with false for
performance (#15293); Grails 9 does not, so instead of defaulting
grails { indy } to true and writing it onto every GroovyCompile task, the
property is now unset by default and the plugin only applies a value the
application set. That stops the plugin from replacing an indy option a
build script puts on its own compile task, and the native-image hook no
longer needs to set an indy convention, since an image's need for
invokedynamic is the compiler's default.
GrailsNativeImageDefaultsSpec hard-coded the Grails 8 default of false
for an application without an image; it and its fixtures now check that
no indy option is set on the compile task. GrailsIndySpec covers the
unset default and both explicit values through a TestKit build. What's
New describes the change without the internal build details, and the
9.0 upgrade guide notes it for applications coming from Grails 8.
Report URL: https://github.com/apache/grails-core/actions/runs/38612531454
With regards,
GitHub Actions via GitBox