The GitHub Actions job "Groovy Snapshot Canary Build" on grails-core.git/8.0.x has succeeded. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: 08082792efe49f92dcb2f4aeef2d9fc140517ba4 / Walter B Duque de Estrada <[email protected]> fix(forge): keep the Grails Data plugin off the generated buildscript classpath (#16575) Generated builds declared grails-data-hibernate5/7 as a buildscript classpath entry (and a buildSrc implementation dependency), a leftover from when the CLI found plugin commands through the build classpath; commands now ship in the companion -cli artifacts the Grails Gradle plugin discovers from the application's dependencies. The plugin pulls in grails-datamapping-core, which registers global AST transformations, so Gradle's embedded Groovy 4 ran them while compiling build.gradle. With the transformations compiled by Groovy 6 that fails at configuration time (NoSuchMethodError NumberMath.remainder). The plugin stays an application dependency only. The 8.0 upgrade guide tells existing builds to drop the classpath entry and names the symptom. Report URL: https://github.com/apache/grails-core/actions/runs/38934470805 With regards, GitHub Actions via GitBox
