jamesfredley commented on PR #15557:
URL: https://github.com/apache/grails-core/pull/15557#issuecomment-4597667728

   Merged the latest `8.0.x` (the `grails-hibernate5-micronaut-bom` split 
#15689) and re-tested every Groovy 5 workaround against the latest 
`5.0.7-SNAPSHOT` (build #7, 2026-06-01) by removing each and confirming the 
failure still reproduces.
   
   **Dropped (upstream bug now fixed):**
   - `Customer` `@GrailsCompileStatic` (hibernate proxy example) - 
GROOVY-11907/11968 are fixed in 5.0.6; `ProxySpec` passes with it restored.
   - `grails-views-gson` 
`StreamingJsonBuilder`/`JsonGenerator`/`DefaultJsonGenerator` shims (222 lines) 
- `groovy.json.StreamingJsonBuilder.StreamingJsonDelegate` is public again, so 
`JsonViewWritableScript` uses it directly. Full `grails-views-gson` suite 
passes.
   
   **Corrected:** restored `@Slf4j` in `NavigableMap` - on the latest snapshot 
the static `LOG` field fails `@CompileStatic` (the inner `NullSafeNavigator` 
can't resolve the outer private static field), so a prior revert of mine was 
wrong.
   
   **Still required (each re-verified failing without the workaround):**
   - VariableScopeVisitor canonicalization NPE guards - 
`:grails-datamapping-tck:compileGroovy` still NPEs.
   - `ConstrainedProperty.DEFAULT_MESSAGES` static-init fallback - still 
resolves null; `DefaultMessageResolutionSpec` fails without it.
   - `Validateable` `defaultNullable()` reflection (GROOVY-11985, open) - trait 
override still lost; 2 specs fail without it.
   - `g.taglib` STC (GROOVY-12041, open) - `g.message(...)` still fails STC; 3 
`GspCompileStaticSpec` cases fail without it.
   - `boot4-disabled` integration tests - controller param-scope under 
`-PgrailsIndy=false` (no upstream fix) plus SiteMesh3/Spring 7.
   
   Description updated to reflect the current remaining set.
   


-- 
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]

Reply via email to