codeconsole opened a new issue, #15258: URL: https://github.com/apache/grails-core/issues/15258
### Expected Behavior I don't understand why the bom was dramatically changed from versioned properties in [7.0.0-M1](https://repo1.maven.org/maven2/org/grails/grails-bom/7.0.0-M1/grails-bom-7.0.0-M1.pom), M2, M3, M4, RC1 and [7.0.0-RC2](https://repo1.maven.org/maven2/org/apache/grails/grails-bom/7.0.0-RC2/grails-bom-7.0.0-RC2.pom) to hard coded versions in [7.0.0](https://repo1.maven.org/maven2/org/apache/grails/grails-bom/7.0.0/grails-bom-7.0.0.pom) After versioned properties had been used over the course of 9 months since M1 was released on 12/23/24 through RC2 on 9/3/25, why such a dramatic breaking change for final 1 month later on 10/15/25? I put a lot of time making a perfectly working bom. Here is [example](https://github.com/codeconsole/grails-bom-demo/commit/d70ce75bb035687eda34837052c0bdc23f2ee5a1) of how easy it was to use **_any version_** of Groovy or Spring Boot after my changes. All you had to do before was add 2 LOC to gradle.properties and everything worked perfectly. ```properties spring-boot.version=3.5.8 groovy.version=4.0.29 ``` How is this done now? Now it appears that when you set a new version for anything, the grails-bom overrides its dependencies and you get mixed versions of dependencies. ### Actual Behaviour _No response_ ### Steps To Reproduce _No response_ ### Environment Information _No response_ ### Example Application _No response_ ### Version 7.0.3 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
