zyro23 commented on issue #16029: URL: https://github.com/apache/grails-core/issues/16029#issuecomment-5513566120
> [@zyro23](https://github.com/zyro23) if you are using Grails 8, is the new bean dsl an option for you? you can define configurations directly in a beans closure of `Application.groovy`. > > The new bean dsl is being [actively maintained](https://github.com/apache/grails-core/pull/16292). thanks for the heads-up! didnot spot that yet. will make myself familiar with it. and from a first look, yes - i guess plugin consumers could override auto-configured configuration classes/beans that way, too. however, to not further broaden the scope of this issue, and as the new bean dsl seems to be independent of `beanRegistrar()`/`doWithSpring`, would you agree that: * configuration classes/beans registered with the legacy bean dsl will no longer be post-processed * and that deserves a mention in the grails-8 docs/upgrade notes as a breaking change * and [`grailsConfigurationClassPostProcessor`](https://github.com/apache/grails-core/blob/v8.0.0-M6/grails-core/src/main/groovy/org/grails/plugins/CoreGrailsPlugin.groovy#L180) is now essentially a no-op and can (i would say should) be removed? -- 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]
