jamesfredley commented on PR #16408: URL: https://github.com/apache/grails-core/pull/16408#issuecomment-5997140490
The failures on `9ee20b6` (the commit before the `9.1.x` merge) were one compile error, repeated by every workflow that builds this tree. `grails-openapi` still imported `org.springframework.aot.generate.ClassNameGenerator`. Spring Framework 7.1, which Spring Boot 4.2.0-M2 brings in, renamed that type to `NameGenerator` with the same `ClassName` constructor. The `grails-core` AOT specs were already updated. `OpenApiBeanFactoryInitializationAotProcessorSpec` was not, so `:grails-openapi:compileTestGroovy` failed and stopped the rest of the build. That was the failure recorded for: - CI: Build Grails-Core (Ubuntu JDK 21) - Functional Tests (Java 21, indy=false) - Hibernate7 Functional Tests (Java 21, indy=false) - Build Grails Forge (Java 21, indy=false) - Code Style - Build Health - End to End (the end-to-end job compiles grails-core before it publishes) `5d7b6adc8d` renames the import and the `DefaultGenerationContext` constructor in that spec to `NameGenerator`. `:grails-openapi:test --tests org.apache.grails.openapi.aot.OpenApiBeanFactoryInitializationAotProcessorSpec` passed all 9 features. Spring Boot 4.2.0-RC1 is not published. GitHub releases and Maven Central still stop at 4.2.0-M2 (2026-09-24). The RC1 wiki page exists and is a draft with its dependency and deprecation sections marked TBD, so this stays on 4.2.0-M2. -- 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]
