jamesfredley commented on issue #16157:
URL: https://github.com/apache/grails-core/issues/16157#issuecomment-5329906005
Follow-up after reading the landed source on `9.0.x` (`cd062bf7`).
**Ordinary 7.x/8.x application source does not need to copy these framework
edits.** Binding, GORM `merge`, transients introspection, Fields, and JSON
views stay on public APIs. The Grails BOM already pulls `groovy-callsite` for
non-indy.
What an upgraded **application** actually has to know:
1. **Spock** - until `2.4-groovy-6.0` is on Maven Central (not published as
of 2026-08-18; Spock master only compiles against Groovy `6.0.0-alpha-2`), any
app that compiles Spock tests on Groovy 6 needs
`-Dspock.iKnowWhatImDoing.disableGroovyVersionCheck=true`. Forge-generated apps
get this automatically.
2. **`grails { indy = false }`** - still the plugin default. Non-indy needs
`groovy-callsite` (BOM-managed).
3. **Micronaut** - island/BOM omitted from Groovy 6 snapshots (#16161).
4. **If the app itself uses** `@CompileStatic` + `||` guards in closures,
`@Canonical` map constructors, or `!(x instanceof T)` under static compile,
those are **Groovy 6 language** issues, not Grails API breaks.
Several catalogue rows are **test-only** in this repo
(`ValidateableTraitSpec`, `GormEntityTransformSpec`,
`TestFormParamsControllerSpec`), not production types. The CI functional-shard
teardown hang on indy=true shard 1 is also CI-only
(`.github/workflows/gradle.yml` + helper scripts) and is not an upgrade concern.
Source comments are still inconsistent (some name beta-2 only, few link
#16157 or a deletion condition). That is the remaining 'treat them the same'
work in the tree itself.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
