I don't feel it's an urgent issue as it's easy enough to remove the setting of the system property in build.gradle. Maybe we can get some more bug fixes into 7.0.2?
/Mattias Den sön 2 nov. 2025 kl 02:56 skrev James Daugherty <[email protected]>: > > Hi Everyone, > > I opened https://github.com/apache/grails-core/pull/15194 to address > configuration not working in 7.x if a spring profile is defined as an > empty string. An example of this scenario is that earlier versions > of grails recommended defining bootRun configuration like this: > > bootRun { > jvmArgs('-Dspring.output.ansi.enabled=always') > String springProfilesActive = 'spring.profiles.active' > systemProperty springProfilesActive, > System.getProperty(springProfilesActive) > } > > When upgrading, this is a legitimate configuration to have, but it > results in the spring.profiles.active property being set to an empty > String instead of null, which triggers the bug the above PR fixes. > > Given that this causes configuration to not load for upgraded > applications, I view this as a critical issue and wish to advocate for > a 7.0.2. > > What are people's thoughts on calling a vote for 7.0.2 after this is merged? > > Regards, > James
