jamesfredley opened a new issue, #16018:
URL: https://github.com/apache/grails-core/issues/16018

   ## Summary
   
   A provisional root SpotBugs baseline produced 287 `BugInstance` entries 
across 51 module reports. The count is provisional because the broad run also 
hits separate task-wiring and detector failures, but the valid XML findings 
should be triaged once execution is stable.
   
   ## Reproduction
   
   ```shell
   ./gradlew aggregateAnalysisViolations --continue \
     -Pgrails.code-analysis.enabled.spotbugs=true \
     -Pgrails.code-analysis.ignoreFailures=true
   ```
   
   Reports are written under `build/reports/code-analysis/spotbugs/`.
   
   ## Largest current groups
   
   | Project/report | Findings |
   |----------------|---------:|
   | `grails-shell-cli-spotbugsMain` | 26 |
   | `grails-spring-security-ui-spotbugsMain` | 21 |
   | `grails-rest-transforms-spotbugsMain` | 18 |
   | `grails-spring-security-spotbugsMain` | 17 |
   | `grails-datamapping-core-spotbugsMain` | 16 |
   | `grails-bootstrap-spotbugsMain` | 14 |
   | `grails-fields-spotbugsMain` | 14 |
   | `grails-data-mongodb-bson-spotbugsMain` | 13 |
   | `grails-data-mongodb-core-spotbugsMain` | 13 |
   | `grails-data-hibernate5-core-spotbugsMain` | 12 |
   | Remaining reports | 123 |
   | **Total** | **287** |
   
   ## Suggested approach
   
   After the SpotBugs execution issue is resolved, regenerate the baseline and 
triage findings by bug pattern and module. Fix true defects first. Scope 
exclusions only to demonstrated generated-code false positives, with comments 
and tests. Add clean modules to a SpotBugs project allowlist incrementally.
   
   ## Acceptance criteria
   
   - The baseline is regenerated after SpotBugs completes without 
infrastructure errors.
   - Every finding is fixed or has a narrow, documented false-positive 
exclusion.
   - Each clean module is added to staged blocking SpotBugs enforcement.
   - Relevant module test suites pass after each cleanup batch.
   


-- 
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]

Reply via email to