Brainstorm: Rewrite Integration Strategy

[Pankraz76]

Rewrite Recipes Workshop

Let’s curate the automated code quality rules together.

1. What We’re Solving

• Eliminate predictable debates (dead code, annotations, test patterns)
• Enforce consistency without manual policing
• Focus PR reviews on business logic, not style or mundane

2. Recipe Candidates

(All recipes are opt-in - we’ll activate per-team preference)

Category	Safe Bets	Controversial But Useful
Cleanup	Unused privates • Unused imports	Final classes
Testing	JUnit5 best practices	AssertJ fluent style
OOP	Missing @Override	Lambda simplification

3. Decision Process

1. Nominate recipes you want enabled (comment below)
2. Veto any problematic transforms
3. Propose custom rules for our domain

---

Why This Works

• No pressure - We enable rules only with team buy-in
• Transparent - Every recipe is documented/linked
• Gradual - Can start with just 2-3 recipes

Want to add:

• Team voting mechanism?
• Timeline for reassessing rules?
• Custom recipe examples?

Let me know how to adjust!

• (re)activate rewrite capability #4708
• https://docs.openrewrite.org/recipes/java/recipes#composite-recipes

refs:

• [S1161] use staticanalysis.MissingOverrideAnnotation to avoid missing @Override on overriding and implementing methods quarkusio/quarkus#48344
• [S1161] use staticanalysis.MissingOverrideAnnotation to avoid missing @Override on overriding and implementing methods quarkusio/quarkus#48344 (review)
• [POC] rewrite-maven-plugin: Introduce OpenRewrite by Moderne apache/maven#2322

@marcphilipp might consider licence escalation.

[Pankraz76]

first introduce then increment.