👋 Hey Grails community!
I’d love to start a discussion about IDE choices for Grails development, especially with the recent news from JetBrains.
JetBrains has opened a YouTrack ticket (IDEA-379825) proposing to mark the Grails plugin as obsolete and stop bundling/maintaining it in future releases (starting around 2026.2).
However, after a quick conversation with them, the Apache Grails team confirmed:
→ The plugin will continue to work in IntelliJ 2026.1 (due this month)
→ The plugin ID will stay the same
→ Details about where the code lives and who maintains it going forward are still being ironed out.
So the future of official JetBrains support is uncertain, and this feels like a good moment to evaluate alternatives.
In our team we’re currently split:
• VS Code for Angular frontend
• IntelliJ for Grails backend (RESTful APIs)
The context-switching is getting painful. At the same time we’re seeing:
• VS Code (and VS Code-based tools like Google’s Antigravity) gaining traction
• Excellent VS Code support for Angular and React in many companies
So the question is:
Does it make sense for us to converge on a single IDE — just VS Code — for the entire stack (frontend + Grails backend)?
A few points I’d really like the community’s real-world feedback on:
• Is VS Code already a viable daily driver for Grails/Groovy work in 2026? Which extensions are people happily using (Groovy LSP, GSP support, Grails run/debug, code navigation, refactoring, etc.)?
• Has anyone fully migrated a production Grails project to VS Code only? How painful or smooth was it?
• With the plugin now in this limbo state (still works for now, but maintenance moving to community/fork), does it still make sense to stay on IntelliJ, or is this the perfect time to go all-in on VS Code for consistency across the team?
• What’s the current community vision/recommendation for IDEs in Grails projects? Any strong success stories or horror stories?
Would love to hear your honest experiences! 🙏
Thanks in advance!
#grails #ide #vscode #groovy #C0NC33WQ0