Add recipe to migrate System.out.print/println to IO.print/println

[e5LA]

What's changed?

Added recipe to migrate System.out.print() and System.out.println() to IO.print() and IO.println()

What's your motivation?

Closes #846.

Checklist

• I've added unit tests to cover both positive and negative cases
• I've read and applied the recipe conventions and best practices
• I've used the IntelliJ IDEA auto-formatter on affected files

[e5LA]

While preparing the PR, I realized we might also want to handle import static java.lang.System.out; and out.println(...).
I’m not sure how common this pattern is - what do you think?

I can look into it and we could add it in a follow-up PR

[timtebeek]

Great to see thanks! I think we can support that without extra effort if we switch to using MethodMatcher :)

[e5LA]

Good point, thanks @timtebeek , I'll update the code.

[e5LA]

@timtebeek - I just realized though, that print() and println() aren't methods on java.lang.System but on out. And out is a field of type java.io.PrintStream.
If we use the matcher against PrintStream we’ll end up matching all println calls on any PrintStream instance, not just on System.out..

Did I miss anything, or do you see a cleaner way to restrict it just to System.out?

[timtebeek]

Thanks a lot for the help here @e5LA ! I've added a few small changes, mostly to reduce duplication, support edge cases, improve performance and remove unused imports past migration. It's also now included in the Java 25 migration going forward. 🎉

[e5LA]

Thanks for the improvements @timtebeek ! Always great to see yours solutions.
Glad it made it into the Java 25 migration.