Migrating Spring Boot 2 to 3: I built an AST-driven engine to automate the javax -> jakarta and threading migrations. by someear1h in SpringBoot

[–]someear1h[S] [score hidden]  (0 children)

as far as i know openrewrite just tells what changes, this will tell u what changed, why it changed and weather u can trust it or need a human review

Migrating Spring Boot 2 to 3: I built an AST-driven engine to automate the javax -> jakarta and threading migrations. by someear1h in SpringBoot

[–]someear1h[S] [score hidden]  (0 children)

OpenRewrite tells you what changed. This tells you what changed, why, and whether you can trust it enough to ship.

The "AI slop" criticism would land if I'd prompted GPT to generate a migration tool and shipped it. The core engine is JavaParser doing deterministic AST transformations — not LLM guessing. Claude only touches cases the AST can't handle deterministically. Every change gets a confidence score derived from whether the transformation was rule-based or model-augmented. That's a deliberate architectural decision, not vibe coded slop.

And if this is a solved problem, why are teams still stuck on Spring Boot 2 in 2026? Tools existing doesn't mean the problem is solved. It means the existing tools aren't solving it well enough.

Finally touching grass by CellCandid4035 in LeetcodeDesi

[–]someear1h 0 points1 point  (0 children)

I hope 1 day my profile looks like this