OPE-930: Add rewrite support for errorprone.refasterrules

[Pankraz76]

checkstyle/checkstyle#17487

OPE-930: Add rewrite support for errorprone.refasterrules

I’d like to propose integrating Google’s Error Prone and its Picnic extension (demonstrated in Automating Away Bugs with Error Prone | PlatformCon 2023) to enable automated bug fixes via rewrite rules. This would complement Checkstyle’s static analysis capabilities by addressing semantic bugs rather than stylistic issues.

Motivation

Error Prone’s refaster/rewrite rules can automatically:

• Fix common bug patterns (e.g., String.equals() misuse)
• Modernize code (e.g., JDK migration helpers)
• Enforce best practices (e.g., null-check improvements)

Real-world adoptions show tangible benefits:

• Apache Kafka’s integration
• Spotless’s implementation

Proposal

1. Add support for errorprone.refasterrules-based rewrites
2. Implement with opt-in adoption (no breaking changes)
3. Include suppression mechanisms for API constraints

Discussion Points

• Need consensus on:
  • Scope of auto-fixes
  • Preferred suppression strategy
  • Integration approach

Next Steps

I’m happy to:

• Prepare a PoC demonstrating the value
• Collaborate on implementation strategy
• Address any concerns about compatibility

[Pankraz76]

kindly request some feedback, thanks.

FYI:
@elharo

[lukasz-jarocki-sonarsource]

Internally we will track the review of this PR under this ticket: https://sonarsource.atlassian.net/browse/OPE-930

[Pankraz76]

waiting for simple enabler:

• OPE-930: Add rewrite support for GradleBestPractices #3391

[Pankraz76]

closing to stop starting start finishing.