jamesfredley commented on PR #16101:
URL: https://github.com/apache/grails-core/pull/16101#issuecomment-5208732827
Updated this to follow the default-off compatibility-bridge pattern from
#16011 rather than enabling the old behavior globally.
The Grails 8 lifecycle remains the default: the application being
initialized is not published to `Holders` before plugin `doWithSpring`.
Applications that still depend on the Grails 7 behavior can temporarily opt in
with:
```yaml
grails:
legacy:
holdersDuringDoWithSpring: true
```
With that property enabled, only the promoted application is exposed during
legacy `doWithSpring` registration, a migration warning is logged, and failure
rollback is ownership-aware. Failed contexts cannot be restored later, and
neither early nor downstream publication overwrites a newer Holder owner.
The upgrade guide and configuration metadata now describe the shim as
transitional support for plugins such as audit-logging 6.0.0, with migration
toward configuration/injection or `beanRegistrar()`. This should address the
concern about surprising default behavior while still giving legacy
applications an explicit escape hatch.
--
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]
