FYI: Here are the PRs for this change:
https://github.com/apache/grails-core/pull/14735
https://github.com/apache/grails-forge/pull/575
See the PR descriptions for how it all works and how to test.
On Sat, May 10, 2025 at 3:03 AM Gianluca Sartori
wrote:
> Okay I understand. My proposal was to
Okay I understand. My proposal was to not broaden the scope for Grails
7. From my point of view the most important thing is to make it work
with the intelliJ IDEA plugin. That to me has a higher impact from a
communication side than a technical one.
We are still fighting the "Grails is dead" thing
Unfortunately since we still ship shell, we have to do something here. My
proposal is how we can move forward with integrating both and long term
look at removing shell again.
Mattias & James F both have also run across caching issues that can lead to
failures too. I would like to propose we st
Hi James & James,
I never took advantage of the live feature of the grails console, out
of curiosity do you know what is/are the main use case/s for it?
On the overall topic, I am not much into it because after the profile
feature removal we created a project template we use to build new
Dueuno E
James,
Thank you for walking through this with me yesterday.
If we look at the collective features and functionality provided across these
tools (grails-shell-cli, grails-wrapper, profiles, grails-forge-cli,
grails-forge-api, start.grails.org, IntelliJ Grails Plugin grails-shell-cli
integratio
Hi Everyone,
James F & I have been discussing the ASF release process. I've previously
mentioned that we have to have reproducible builds to use GitHub actions.
We have made the discovery that it's impossible to have reproducible builds
in forge due to this bug: https://github.com/oracle/graal/i
