The GitHub Actions job "Licensing - RAT Report" on grails-core.git/fix/aot-live-instance-beans-8.0.x has failed. Run started by GitHub user codeconsole (triggered by codeconsole).
Head commit for run: bc537807e332ba021f6a332a51bc63f7418c724a / Scott Murphy Heiberg <[email protected]> Document ahead-of-time processing and cover it with tests AOT support is opt-in and needs configuration that is not guessable - the Spring Boot AOT plugin, and generation in production mode, without which the url mappings holder takes its reload-mode proxy shape and generation fails naming a bean unrelated to anything in the application. The deployment guide now covers enabling it, what changes at runtime, and the limitations: registrar-contributed beans are not generated, definitions holding live objects cannot be generated, abstract definitions are excluded, and AOT alone does not make an application native-image ready. Two layers of coverage, because the failures differ in kind. CoreGrailsPluginAotSpec runs the real generator over the core plugin's bean definitions, so a definition holding a live instance fails the build. It also covers the configuration class post-processor being registered normally and withheld when generated artifacts are in use, which no existing test reached. A fourth case registers a definition holding a live instance and asserts generation rejects it, so the check above cannot pass vacuously. Generation succeeding does not mean the application starts, and the post-processor condition is a runtime-only behaviour. The grails-test-examples aot application therefore runs processAot and then starts the packaged jar with spring.aot.enabled=true, asserting the beans an AOT context must still contain. Its check task fails the build if either half regresses. Report URL: https://github.com/apache/grails-core/actions/runs/30963765626 With regards, GitHub Actions via GitBox
