The GitHub Actions job "Validate GitHub Actions" on grails-core.git/chore/automate-project-conventions has failed. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: 1d6d2396d10d31c93f274959300da23c3b75e6b6 / James Daugherty <[email protected]> Opt modules into PMD and SpotBugs with enablePmd() and enableSpotbugs() The opt-in was a property, grailsCodeAnalysis { pmdEnabled = true }, which the plugin could only read after the module's build script ran, so it configured PMD and SpotBugs in afterEvaluate. Build scripts then had to wrap any customization of the pmd* and spotbugs* tasks in afterEvaluate too, and the plugin failed when applied after the project was evaluated. Modules now call enablePmd() or enableSpotbugs(), which apply and configure the tool immediately, as java { withSourcesJar() } does. The Gradle properties are read in apply(): the selected-projects property and an all-project true enable the tool up front, and an all-project false makes both methods do nothing. Report locations and the build-directory exclude are resolved lazily, so a reports directory or build directory set later in the script still applies. The docs drop the afterEvaluate caveat and state that the all-project property, when set, wins over both the selected-projects property and the module opt-ins. Report URL: https://github.com/apache/grails-core/actions/runs/36153830246 With regards, GitHub Actions via GitBox
