You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@grails.apache.org by GitBox <gi...@apache.org> on 2026/06/29 23:08:07 UTC
[GH] (grails-core/feat/configurable-bean-overriding-circular-refs): Workflow run "Licensing - RAT Report" is working again!
The GitHub Actions job "Licensing - RAT Report" on grails-core.git/feat/configurable-bean-overriding-circular-refs has succeeded.
Run started by GitHub user codeconsole (triggered by codeconsole).
Head commit for run:
e3b5acf55af0b93d5b6390e55640343391185b55 / Scott Murphy Heiberg <sc...@alwaysvip.com>
feat: make bean definition overriding and circular references configurable
GrailsApp and the unit-test harness GrailsApplicationBuilder hardcoded
allowBeanDefinitionOverriding(true) and allowCircularReferences(true),
silently overriding any value set through the standard Spring Boot properties
spring.main.allow-bean-definition-overriding and
spring.main.allow-circular-references.
Both now resolve those properties from the configured environment, defaulting
to true to preserve Grails' historical behavior (a plain Spring Boot app
defaults both to false). Applications can opt into stricter startup semantics
via application.yml.
- grails-core: GrailsApp.createApplicationContext reads both flags from the
configured environment.
- grails-testing-support-core: GrailsApplicationBuilder.createMainContext reads
the same properties after configuration data is loaded and before refresh.
- docs: new section in the Application class configuration guide.
- tests: GrailsAppContextOverridingSpec (grails-core) and
GrailsApplicationBuilderContextOverridingSpec (grails-databinding). The latter
documents that disabling bean definition overriding fails a Grails unit
context with BeanDefinitionOverrideException, which is why the default is true.
Report URL: https://github.com/apache/grails-core/actions/runs/28408556121
With regards,
GitHub Actions via GitBox