jamesfredley opened a new pull request, #16298: URL: https://github.com/apache/grails-core/pull/16298
## Description Restores 9.0.x CI after merging 8.1.x. Before that merge, 9.0.x CI was already red on Forge (`mainClassName`) and `publishMicronaut`. The merge then added a Groovy 6 static-compile failure in `GrailsWebDataBinder` that took down Core, Forge, functional, Hibernate, MongoDB, Redis, Neo4j, Spring Security, and Code Style jobs. This PR fixes the three unique root causes. ### Groovy 6 collection binding compile `GrailsWebDataBinder` now hoists `item == null || referencedType.isAssignableFrom(...)` into a boolean local, matching the existing array/map workaround. Groovy 6.0.0-beta-2 STC otherwise collapses `||` flow state inside the closure to `void` and fails with `ArrayList#leftShift(void)`. Verified: `./gradlew :grails-web-databinding:compileGroovy -PskipCodeStyle` ### Forge shadow scripts on Gradle 9.7.1 The Application plugin no longer has `mainClassName`. Setting that extra property made `:grails-forge-web-netty:startShadowScripts` fail with `You can't map a property that does not exist: propertyName=mainClassName`. The plugin now sets extra property `mainClass`. Verified: `cd grails-forge && ./gradlew :grails-forge-web-netty:startShadowScripts -PskipCodeStyle` ### Micronaut island is not on Groovy 6 `settings.gradle` only includes `grails-micronaut` / `grails-micronaut-bom` when the build uses Groovy 5. 9.0.x uses Groovy 6, so `publishMicronaut` and the matching release/reproducibility paths invoked missing projects. Those jobs and the dual-JDK Micronaut docs/scripts are removed on this branch. ## Contributor Checklist - [x] This PR addresses failing 9.0.x CI after the 8.1.x merge-up - [x] This PR targets `9.0.x` - [x] Targeted compile/Forge verification passed locally - [x] No unrelated reformatting -- 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]
