Copilot commented on code in PR #80: URL: https://github.com/apache/comdev-events-site/pull/80#discussion_r4031400109
########## source/events/2026/community-over-code/groovy-grails.md: ########## @@ -31,12 +31,9 @@ the two. Specifically, we'd like to come away with a plan (and as much code as we can manage) for a *single* Grails application generator instead of two, plus an agreed CLI command structure going forward. -Existing issues that cover part of this — the list isn't exhaustive, and -we expect to write more during the event: +Issues listing details: -* [grails-core#15301](https://github.com/apache/grails-core/issues/15301) — Unify and simplify CLI command architecture -* [grails-core#14081](https://github.com/apache/grails-core/issues/14081) — Make profiles optional for the Grails-Shell CLI -* [grails-core#14944](https://github.com/apache/grails-core/issues/14944) — Forge vs profile dependencies for `plugin` and `web-plugin` +* [grails-core#16348](https://github.com/apache/grails-core/issues/16348) — one Grails application generator and one agreed CLI command structure Review Comment: The linked #16348 working document explicitly says that #15301, #14081, and #14944 “remain useful”; all three are also still open. Removing them here makes the event page hide the actionable slices that the new inventory points readers to, so this does not look like an outdated-reference cleanup. Please retain these links and add #16348 as the overview issue (or otherwise link the three actionable issues from this section). -- 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]
