Forgot to link to the Grails PR that could work around this for now: https://github.com/apache/grails-core/pull/15963
I need feedback on the PR to continue with the 8.0.0-M3 release. Separately, I think Scott has found the cause to #2. he's researching a fix. On Fri, Jul 10, 2026 at 3:21 PM James Daugherty <[email protected]> wrote: > > FYI: concerning #1, these are the jars that differ: > > grails-data-graphql-8.0.0-M3.jar > grails-datamapping-core-test-8.0.0-M3-tests.jar > grails-datamapping-tck-8.0.0-M3.jar > grails-rest-transforms-8.0.0-M3.jar > grails-scaffolding-8.0.0-M3.jar > grails-spring-security-8.0.0-M3.jar > grails-spring-security-acl-8.0.0-M3.jar > grails-spring-security-oauth2-8.0.0-M3.jar > grails-spring-security-rest-8.0.0-M3.jar > grails-spring-security-ui-8.0.0-M3.jar > > I've opened https://issues.apache.org/jira/browse/GROOVY-12146 with a > proposed fix at https://github.com/apache/groovy/pull/2687 (trying to > avoid the treemap approach that was originally reverted) > > As to the 8.0.0-M3 release, do we wait for Groovy or do I add a post > processing script that will let us diff during the milestone releases > to work around this issue? > > > > On Fri, Jul 10, 2026 at 2:45 PM James Daugherty <[email protected]> wrote: > > > > Hi Everyone, > > > > While staging 8.0.0-M3, I've run into 2 issues: > > > > 1. the build isn't reproducible (first build with groovy 5, so it's > > likely related) > > 2. the create-apps aren't being styled correctly (this could be > > sitemesh, enableWebMvc, or the asset pipeline update) > > > > Concerning #1, it appears to be annotation member related. I have a > > work around locally (groovy compile script), but I don't think it's > > the right solution. I also have a modification to the verify script > > to ensure the differences are equivalent, but I'm not sure if that's > > enough. Once I know the groovy issue more, we can decide whether to > > wait for a groovy fix or to use a workaround to release. > > > > Concerning #2, Scott is researching. > > > > -James
