jamesfredley commented on PR #15557: URL: https://github.com/apache/grails-core/pull/15557#issuecomment-4500982445
### CI fix: pin to released Groovy 5.0.6 (commit 423022f17c) All 19 CI failures on the previous run (`a000a5fa12`) were a single root cause - **Apache's snapshot retention has purged the `5.0.6-SNAPSHOT` artifacts**. The folder at `https://repository.apache.org/content/groups/snapshots/org/apache/groovy/groovy/5.0.6-SNAPSHOT/` contains only `maven-metadata.xml.{md5,sha1,sha256,sha512}` hash placeholders dated `Fri May 08 22:46:47 UTC 2026`; every per-build JAR returns 404. Every Build / Functional / Hibernate5 / Mongodb / Forge job died at the dependency resolution step with: ``` Could not find org.apache.groovy:groovy:5.0.6-SNAPSHOT Could not find org.apache.groovy:groovy-bom:5.0.6-SNAPSHOT Could not find org.apache.groovy:groovy-templates:5.0.6-SNAPSHOT Could not find org.apache.groovy:groovy-xml:5.0.6-SNAPSHOT Could not find org.apache.groovy:groovy-json:5.0.6-SNAPSHOT Could not find org.apache.groovy:groovy-sql:5.0.6-SNAPSHOT ``` `5.0.6` was released to Maven Central on 2026-05-04 and is resolvable from `repo1.maven.org`. The 4 post-tag commits on `GROOVY_5_0_X` (javaparser bump, jackson bump, dep-metadata update, and GROOVY-11996's `groovy.truth.file.exists.enabled` opt-out flag) are not load-bearing for any of the 6 remaining workarounds, so pinning to the release is functionally equivalent for this PR and unblocks CI immediately. Both `groovy.version` entries in `dependencies.gradle` were updated (the main bom + the `grails-micronaut-bom` `strictly`-override). The snapshot repo declaration in `settings.gradle` is left in place so the `groovy-joint-workflow` job can still swap in an upstream Groovy snapshot when needed. Verified locally on the released 5.0.6: ``` > Task :grails-test-examples-compile-static:integrationTest BookServiceSpec > test validateBooks method PASSED JVM 21.0.10 | Grails 8.0.0-SNAPSHOT | Groovy 5.0.6 | Spring Boot 4.0.5 | Spring 7.0.6 ``` ### Open-PR overlap check Audited every open PR against `8.0.x` for duplication: | PR | Branch | Touches `groovy.version`? | Conflict / overlap with this fix | |---|---|---|---| | #15183 (matrei, `groovy-5`) | `groovy-5` | Yes - pins to `5.0.5` | Older Groovy 5 attempt, on 5.0.5 (behind us), currently CONFLICTING + 25 failing checks. No overlap; that branch is orphaned by this one. | | #15654 (jdaugherty, `8.0.x-stage-hibernate7`) | `8.0.x-stage-hibernate7` | No | Independent (Hibernate 7 stage 1). | | #15664, #15652, #15619, #15467, #15465 | various | No | Docs / BOM refactor / RELEASE.md / TagLib syntax. None touch `groovy.version`. | So this fix is unique and not duplicating any other in-flight PR. ### PR description updated Bumped audit date to 2026-05-20, updated the target stack row + status paragraphs to reflect the snapshot purge and the pin-to-release decision, added a bullet under `## Forge / generated-app coverage` for the new `compile-static` test app from #15294, and updated the GROOVY-11996 cell in the workarounds table to note that the real-fix rewrites do not depend on the opt-out flag. CI is queued on the new HEAD; will report back if the build surfaces issues beyond the dependency-resolution block. -- 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]
