Grails 7 Scope - Remove Micronaut Context #13517
Replies: 4 comments 17 replies
-
Removing Micronaut Context as the parent context of the Spring Boot context means you would not longer be able to:
|
Beta Was this translation helpful? Give feedback.
-
If Micronaut was to be come a plugin, so it became an optional plugin, I would see that as a big plus. |
Beta Was this translation helpful? Give feedback.
-
My biggest issue with Micronaut in Grails is the fact thait's not clear WHY Micronaut is a worth addition for the framework (here is the link of the current user guide: https://docs.grails.org/6.2.0/guide/single.html ) on the main documentation. This is the main problem: for the newbie (and I'm not a newbie, I'm a Grails user since the beginning and even wrote a bookt about it "Falando de Grails") it's not clear the bennefits of Micronaut. And I must confess, even for me is not clear. One of the nicest features we could have was a faster startup of the application. And the fact is that even today we still don't have this. |
Beta Was this translation helpful? Give feedback.
-
There is a work-in-progress PR currently updating to Micronaut 4.5.3 #13545 |
Beta Was this translation helpful? Give feedback.
-
The grails team have been discussing whether or not it is worth keeping the Micronaut Context as the Parent Context in Grails (since Grail 4.x). This has caused issues in development regarding configuration loading , among others. It also has led to preventions on usages of reloaders like the hotswap-agent (those may be resolvable however). The thought is to let Grails be based on spring and not mix the other framework in. That being said micronaut can still be used within the project in a more standalone manner.
46 votes ·
Beta Was this translation helpful? Give feedback.
All reactions