jamesfredley opened a new pull request, #15686: URL: https://github.com/apache/grails-core/pull/15686
## Step 1 (PR-G): grails-code-analysis convention plugin + violation aggregation Carved out of the Hibernate 7 Step 1 PR (#15654) per review feedback from @matrei that the static-analysis tooling should be introduced in its own focused PR. ### What this adds - **`grails-code-analysis`** convention plugin (PMD + SpotBugs) applied to 96 subprojects, with `GrailsCodeAnalysisExtension`. - **`grails-violation-aggregation`** root-only plugin that consolidates per-module Checkstyle/CodeNarc/PMD XML reports into Markdown summaries under `build/reports/violations/` via an `aggregateStyleViolations` task. - **`grails-code-style`** plugin improvements split cleanly from analysis: enable/disable properties, a `codenarcFix` task, a test-styling toggle, and a resource-path rename to `grails-code-style` (PMD config under `grails-code-analysis`). - `codeanalysis.yml` workflow; `codestyle.yml` switched to the aggregated report format. - `pmdVersion` / `spotbugsPluginVersion` properties and the `violation-fixer` skill. ### Notes - JaCoCo coverage is intentionally **not** in this PR. It layers on top of the `grails-violation-aggregation` plugin introduced here and is carved out separately (PR-H). - Verified with `cd build-logic && ../gradlew :build-logic:test` (plugin Spock specs pass). ### Why Splitting this from #15654 keeps the Hibernate 7 baseline clone focused on the actual h5 -> h7 work and lets the project review/decide on the analysis tooling independently. Assisted-by: claude-code:claude-4.7-opus -- 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]
