borinquenkid opened a new pull request, #16575: URL: https://github.com/apache/grails-core/pull/16575
## What Grails Forge no longer adds `grails-data-hibernate5` / `grails-data-hibernate7` to the generated `build.gradle` `buildscript` classpath (nor to `buildSrc`). The plugin stays an ordinary application dependency. `GrailsDataHibernate5/7` features and their specs are updated; `whatsNew` and the 8.0.x upgrade guide gain a section telling existing builds to drop the entry. ## Why The entry was a leftover from when the CLI found a plugin's commands through the build classpath; commands now ship in companion `-cli` artifacts that the Grails Gradle plugin discovers from the application's dependencies. With the plugin on the `buildscript` classpath, `grails-datamapping-core`'s global AST transformations run inside the Groovy that Gradle embeds while compiling `build.gradle`; once those transformations are compiled by Groovy 6 that fails at configuration time (`NoSuchMethodError ... NumberMath.remainder`, seen in the Build Grails Forge job: `CreateDomainClassCommandSpec` and the other command specs). This is independent of the Java-to-Groovy migration (#16351) but surfaced while splitting it, so it is its own PR against `9.0.x`. ## Verification - Cherry-pick of the fix verified on the migration branch; the Forge build is a separate Gradle build and its specs are run by the Forge CI job (no local test run). 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
