We meet every week via Google Meet. The times alternate each week to
encourage attendance from multiple time zones. Each week we will provide
a summary here to facilitate historical preservation & further discussion.
Times for next three Apache Grails Planning meetings:
7/23/2025:
https://www.worldtimebuddy.com/?qm=1&lid=8,6,5,12,30,1819729,2207259&h=8&date=2025-7-23&sln=14-15&hf=1
7/30/2025:
https://www.worldtimebuddy.com/?qm=1&lid=8,6,5,12,30,1819729,2207259&h=8&date=2025-7-30&sln=7-8&hf=1
8/6/2025:
https://www.worldtimebuddy.com/?qm=1&lid=8,6,5,12,30,1819729,2207259&h=8&date=2025-8-6&sln=14-15&hf=1
If you would like to join this meeting, you can do so here:
https://meet.google.com/her-tjpt-xmf
Notes:
1. 7.0.0-M5
a. The ASF release report tool worked for M4, but not for M5
i. This may be due to the files being published to incubator vs top level
ii. Advised to ignore tool for M5, and wait for graduation
1. After graduation we can go back and add it
iii. redis and spring-security plugins have not been reported either
iv. creating duplicates on dist.apache.org would create confusion and
then removing the duplicate would lead to more confusion
2. RC1 Major Release Blockers:
a. i18n plugin - resolved
b. Metadata - resolved
c. Optional Micronaut Compatibility
i. Does anyone have experience and time to assist?
ii. Notes from James Daughtery: “the existing code won’t work because of
the spring app builder changes in 3.0. I think we have to do what
micronaut did - create a GrailsApplicationContext that can be passed to
the spring application builder.”
iii. https://github.com/apache/grails-core/issues/14017
3. Spotless / Checkstyle & Code Reformatting
a. https://github.com/apache/grails-core/pull/14903
4. Jérôme Prinet from Gradle helped us with build performance
a. https://github.com/apache/grails-core/pull/14895
5. grails-plugins
a. create policy around org.grails.plugins vs io.github.gpc vs plugin
developers own central account namespace
b. Consider a namespace of org.grails.gpc to replace io.github.gpc
i. Separate secrets from org.grails.plugins
ii. Same release procedure as org.grails.plugins
6. With Grails 7.0.0-M5 released, it's now time to prepare M5 releases
for the other 3 projects:
https://github.com/apache/grails-spring-security ,
https://github.com/apache/grails-redis and
https://github.com/apache/grails-quartz . If you have some time to take
one of these on, please reply in this thread.
a. A goal during this preparation is to remove the grails dependencies
from the published plugin POM and Gradle modules, to avoid the need to
re-release just to change the grailsVersion, by transitioning to
compileOnly on all Grails dependencies and disabling spring dependency
management (it adds the dependencyManagement block in pom.xml).
b. See examples:
i.
https://github.com/wondrify/asset-pipeline/blob/5.0.x/asset-pipeline-grails/build.gradle
ii.
https://github.com/grails-plugins/grails-audit-logging-plugin/blob/6.0.x/plugin/build.gradle
7. https://www.infoq.com/news/2025/07/java-news-roundup-jul07-2025/
a. 37 visits to the website so far:
https://analytics.apache.org/index.php?module=CoreHome&action=index&date=yesterday&period=day&idSite=79#?period=month&date=2025-07-07&idSite=79&category=Referrers_Referrers&subcategory=Referrers_WidgetGetAll
b. Does anyone have a contact as InfoQ to ask about a Grails 7 final
article?
i. Søren has contacted Guillaume Laforge for a contact.
8. hotswap agent status
a. https://github.com/apache/grails-core/issues/13669
9. spring boot developer tools
a. still viable for most projects, unless very large
b. included by default in Grails 5 and grails shell (profile based)
generated applications in 6.2.1+, including 7.0.x
c. James Fredley will adjust it to be default from forge also
i. Users with larger projects are more likely to know to remove it
10. database migration plugin
a. some scripts are missing
b. https://github.com/apache/grails-core/issues/14918
