James Fredley

https://github.com/grails/grails-core/pull/13702/files#diff-d7674e06b1294ce8a4fae2ab1606c48dbd1ff7c1eddb037dfd868dcc59f8fa7e is still in the latest code And these two open tasks https://github.com/grails/grails-doc/issues/912 https://github.com/grails/grails-core/issues/14017

This ticket can close before the [grails-doc](https://github.com/grails/grails-doc/issues/912) and [grails-functional-tests](https://github.com/grails/grails-core/issues/14017) tickets https://github.com/grails/grails-core/blob/7.0.x/grails-test-suite-persistence/src/test/groovy/grails/web/databinding/GrailsWebDataBindingListenerSpec.groovy#L19 is the only outstanding test that broke when micronaut was removed, that I am aware of.

https://github.com/bertramdev/asset-pipeline/issues/355

https://github.com/grails/grails-core/pull/13807 - for grails-database-migration

https://github.com/apache/grails-core/pull/14970

Currently blocked by https://github.com/apache/grails-core/issues/13669#issuecomment-3066110262

The following example project has been updated with the latest Grails 7 changes: https://github.com/jamesfredley/hotswap-demo - this automatically installs and runs the right JDK (only JETBRAINS 17 and 21 work), downloads...

https://github.com/HotswapProjects/HotswapAgent/issues/581 is relevant Loading new domain classes, reloading changed domain classes and resolving all of the logged errors may require changes to https://github.com/HotswapProjects/HotswapAgent and it's plugins

@jaGarcia editing an existing service reloads. Creating new service requires a restart.

It sounds like https://github.com/jamesfredley/hotswap-demo is on par with expectation from Grails 5.