We meet every week via a google meeting. Each week we will provide a
summary here to facilitate historical preservation & further discussion.
If you would like to join this meeting, please see:
https://calendar.google.com/calendar/r?eid=MGNnc29hYjFvYW1ndjI5ODJiZXRwZGRjbmMgamFtZXNmcmVkbGV5QHRyaXVtcGhpbnRlcmFjdGl2ZS5jb20&ctok=amFtZXNmcmVkbGV5QHRyaXVtcGhpbnRlcmFjdGl2ZS5jb20
Notes for this week following:
- The Apache migration status was discussed:
- Repos are migrated
- Initial snapshot Secrets are setup
- Grails 7 Project (https://github.com/orgs/grails/projects/3) is
still being migrated by ASF Infrastructure. Infrastructure stated that
they haven't found a way to programmatically migrate this and
are exploring
other options.
- We recapped the artifact id / group id proposal (
https://lists.apache.org/thread/39ko9qns6lo0jkfcotskm4yob0zwbw4b)
- We have decided to hold off on repackaging grails classes in Grails 7
due to the discussion in the previous mentioned thread. We will revisit in
Grails 8.
- Mattias is working on a composed build for Grails-core and then we
will proceed updating the projects.
- We began discussing the spring boot release schedule and what that
means for Grails releases:
- Grails will likely adhere to spring boot's schedule to ensure
supported libraries.
- The "catch up" required for Grails 7 may delay an exact 1:1 match.
- Grails 7.1 will be Spring Boot 3.5
- Grails 8 will be Spring Framework 7, Spring Boot 4
- We discussed the recent ticket movement on various IntelliJ issues
- Multiproject builds should be fixed in 2025.1
- We have discussed alternative IDE support, including:
- Including a GDSL with Grails releases for community IDE support
- Switching to annotations so processors can be used and IDE
support can be "out of the box"
- Exploring other IDE options:
- We know that there has been some luck with people
implementing a plugin for vsCode.
- gorm-hibernate6 work has started by Walter, see
https://github.com/grails/grails-data-hibernate6 - the hibernate 6
branch.
- Work will be reviewed as a whole once the initial migration has
happened.
- We further discussed hibernate support:
-
Grails hibernate6 support will likely start with hibernate 6.6 and
support Grails 7.0.x and 7.1.x initially. Grails 8, which will
be based on
Spring 4.0.x, will support Hibernate 7 with Jakarta persistence
3.2, so as
early as Nov 2025, earlier if looking at milestones,
grails-data-hibernate7
work could begin. Grails 8 would need to be tested against
grails-data-hibernate5, grails-data-hibernate6 (if it's ready) and then
considered for grails-data-hibernate7 (later released date).
- We reviewed the asset plugin history
- David Estes provided an update on the plugin and stated that it
will be moving to it's own GitHub organization
- We discussed the numerous layout issues that have been found.
- Most seem related to the sitemesh3 upgrade. Some relevant commits
/ PRs that need reviewed to restore functionality (or rather the
tests for
it):
- gsp commit: 17f34ba82fc6660a803b9a960e00ccfac93f8d9e
- https://github.com/apache/grails-core/issues/13058
- https://github.com/grails/grails-gsp/pull/459
- https://github.com/apache/grails-core/pull/13492/files
- We found tests in these PRs that seem to have covered some of the
reported bugs. We will explore restoring a version of them for sitemesh3.
- Given that we are renaming the coordinates for grails-cache, we agreed
to start a discussion on migrating grails-cache to grails-core.
