Our project is currently using M3 and a colleague ...
# questions
u
Our project is currently using M3 and a colleague of mine had created an experimental branch using RC2 using workarounds to we are not pushing to any external environment, yet.
j
I would strongly urge you to not use milestone releases at this point - the sitemesh fixes that came in rc1 were significant. As for updating dependencies, we are trailing Spring Boot by less than a month now. Updating spring versions before spring boot does may come with unknows
what workarounds did you need?
j
u
@James Fredley, thanks I followed that documentation when I did my local experiments with M4.
u
@jdaugherty my colleague added the following in our
build.gradle
Copy code
// required for seed-me-gradle until they update their classpath
        substitute module('org.grails:grails-core') using module("org.apache.grails:grails-core:$grailsVersion")
        substitute module('org.grails:grails-web-boot') using module("org.apache.grails:grails-web-boot:$grailsVersion")
        substitute module('org.grails:grails-dependencies') using module('org.apache.grails:grails-dependencies:7.0.0-M5')
        substitute module('org.grails:grails-plugin-domain-class') using module("org.apache.grails:grails-domain-class:$grailsVersion")
to avoid upgrading seed-me to the new Grails. When I did my M4 tests I had seed-me ported to M4 in my local maven.
u
@jdaugherty we are not in production, we'll go with 7.0.0, someone you may know whose goes with the name of David Estes started the project using 7.0.0-M3.
j
It's all good, I've had a basic Grails 7 app in prod since October as a canary, I do wish it was more complex as it would have caught more issues. It's currently running on Java 24 with virtual threads with 1-2 weeks of changes post RC2. I don't recommend that for critical apps.
u
that fact the name of our repository ends with POC tells a lot. 🙂
❤️ 1
j
I can tell you there are hard breaks between the milestone & RC. I wouldn't mix the grails versions - they're meant to be updated together during major development.
i'm guessing you have an old plugin that's using the old api's?
the only reason the above would work is if the plugin isn't actually using the api's the changed (a lot of plugins included the world instead of what they needed)
u
I'm trying to make a list of them
🎉 1