Scott Murphy

This is being caused by eager initialization of UrlMappings from a proxy. It does not happen in a live configuration, but should still be addressed. The offending code is here:...

https://github.com/grails/grails-core/pull/13845

@jamesfredley https://github.com/grails/grails-core/pull/13845 wasn’t supposed to fix the problem. It just identifies the cause and isolates it

These really have nothing to do with the plugin. These "bugs" are related to internal design in Grails. https://github.com/grails/grails-core/pull/13908

### Tested in Grails 6.2.2 [Fields plugin tags ](https://grails-fields-plugin.github.io/grails-fields/ref/Tags/display.html)do not autocomplete and show up red. asset:image,asset:link,asset:stylesheet... asset pipeline tags to not autocomplete and show up in red Seems like base...

Seems like debugging Groovy in IntelliJ is now a nightmare. In one method call, there is literally 28 useless submethods in a stack trace. 

It won't get picked up unless you have `@ComponentScan` on your Application class. ```groovy @CompileStatic @ComponentScan class Application { static void main(String[] args) { Grails.run(Application, args) } } ``` https://guides.grails.org/grails-configuration-properties/guide/index.html

@rainboyan in some cases developers might not want `@ComponentScan` or `@EnableAutoConfiguration` enabled by default with `@SpringBootApplication`. An alternative for the above configuration would be to enable it specifically: ```groovy @CompileStatic...

@rainboyan if you used `@ComponentScan`, it scans all your class files. `@Import` will just load the individual configuration. Using `@Import` is also more predictable behavior. Here we are only talking...

> In Grace, this is no longer needed, when the `Application.groovy` compiled, the `@SpringBootApplication` annotation will be added, just like Spring Boot does. @rainboyan using Grace [2023.0.0-M6](https://github.com/graceframework/grace-framework/releases/tag/v2023.0.0-M6) I created a...