Hi, James,
I'm new to the group. Thanks for handling the Grails development! I don't
see the meeting dates, times. Can you send?
Thanks,Clark Meier
On Wednesday, January 14, 2026 at 08:20:38 AM CST, James Daugherty
<[email protected]> wrote:
We meet every week via a google meeting. 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. If you would like to join this meeting, you can
do so here: https://meet.google.com/her-tjpt-xmf
* Responding to bug tickets & minor updates to polish the state of
Grails 7 has been the focus of the developers currently. We are
trying to focus on quality & plugins (not necessarily hosted at the
ASF) to help the general Grails community. Volunteers are welcome to
assist.
* Geb / Grails-Geb Merger proposal
- discussion on groovy mailing list initiated by Carl.
- there is desire from both Grails & Groovy developers to merge the
testcontainer support Grails added directly into Geb
- James D added Mattias & Jonas for feedback. Carl is leading that
effort. Groovy team is open to feedback which allows us to ensure we
can minimize the code we have in Grails-Geb.
* grails-bom issue
- https://github.com/apache/grails-core/issues/15302
- likely due to the property name calculator not selecting more
specific properties
- James D to take a look in the coming week
* Quartz
- 2.5.1 has known column case comparison issues. Next version of
spring-bom will update to 2.5.2 addressing these issues.
* javax to jakarta for Grails Plugins
- Reminder for plugins that have not been converted, useful plugin
created by Netflix:
https://grails.apache.org/docs/snapshot/guide/upgrading.html#_12_2_javax_jakarta
* url-mappings-report-broken
- will be fixed in 7.0.5 via https://github.com/apache/grails-core/issues/15286
* invoke dynamic performance
- feedback on Grails 7 has shown invoke dynamic performance is causing problems
- we have reached out to the Groovy developers to start a wider
discussion and shown people how to disable for Groovy 4
(https://github.com/apache/grails-core/issues/15293)
* Groovy 5 Update
- Grails is still not compiling, likely due to the jline 3 upgrade
- Next steps for Grails adoption is to get compiling with Jline 3
https://github.com/apache/grails-core/issues/13752
* Groovy 4 Issues
- Groovy has been holding off on 4.0.30 for some last minute fixes;
release will likely occur in the next week
- New issue found: https://issues.apache.org/jira/browse/GROOVY-11818
- Will likely go in with Grails 7.0.6
* 7.0.5 Release
- numerous fixes, but we do not have the bom or micronaut fix
- will proceed with 7.0.5 due to spring boot upgrade & security updates
- may quickly release 7.0.6 after depending on fix availability for
Grails bom fix
* Micronaut Integration update
- still need a way to reflect beans created in the Micronaut context
into the Spring context without duplicating.
- Initial work to get Micronaut working better is still at
https://github.com/apache/grails-core/tree/micronaut-fixes
- Need a volunteer for this issue or wait until someone frees up to look at it.
- Suggestion to reach out to Graeme / Sergio for assistance; will follow-up
* IP Blocks
- bad actors have been using github actions which have caused those
IPs to be blocked again
- we need to bring this issue forward in the next round table with
infrastructure
- one possible solution is self hosted runners
- would be nice if we could somehow customize our gradle api requests
and include an identifier - this could be used to help locate bad
actors within the ASF or in the wider Github community
- previous gradle ticket rejecting this request:
https://github.com/gradle/gradle/issues/1521
* g.render is generating different JSON in Grails 7 vs 6
- https://github.com/apache/grails-core/issues/15306
- likely due to the groovy property changes, needs debugged for next steps
* mimetype discussion follow-up
- we need to create a ticket for this proposal for Grails 8
- main issue Scott brought forward previously is setting empty
configuration does the opposite of what's expected
* Grails 8
- next major steps:
- build support for selecting hibernate version
- Groovy 5 support
