The GitHub Actions job "CI - Groovy Joint Validation Build" on grails-core.git/feat/plugin-dowithspring-method has succeeded. Run started by GitHub user codeconsole (triggered by codeconsole).
Head commit for run: 21a937de06ccd318036e1d7cb1b0370c243225dd / Scott Murphy Heiberg <[email protected]> Add method-based doWithSpring(BeanBuilder) plugin hook Introduce a statically-compilable alternative to the closure-returning doWithSpring() hook on the Plugin base class. Plugins can now register beans by overriding doWithSpring(BeanBuilder) and calling the builder directly, instead of returning a closure whose delegate the container wires up at runtime. The new hook is a no-op on the Plugin base class, and DefaultGrailsPlugin invokes both hooks for Plugin descriptors, so a plugin may override doWithSpring(), doWithSpring(BeanBuilder), or both. The legacy closure-returning form and the legacy closure-property form on non-Plugin descriptors remain fully supported. The hook is intentionally scoped to the Plugin class and is NOT added to the GrailsApplicationLifeCycle interface: that interface is map-coerced in the testing support (GrailsApplicationBuilder builds `[doWithSpring: {...}] as GrailsApplicationLifeCycle`), and Groovy's map-to-interface proxies do not honour Java default methods, so an interface-level hook would break every unit test that builds an application context. Adds PluginDoWithSpringMethodSpec covering the Plugin no-op, direct method-form registration, and the DefaultGrailsPlugin dispatch for the method form, both hooks together, and the legacy closure form. Documents the new hook in the plugin runtime-configuration guide. Report URL: https://github.com/apache/grails-core/actions/runs/28965034388 With regards, GitHub Actions via GitBox
