These only delegate to UpgradeJavaVersion, but had a displayName and description that were Maven specific, despite also updating Gradle build files, and SourceFileMarkers after 9c6acfb5c5f2c942f8660a687b5263b3841c65ac.
I'd say it's unlikely folks have specifically included these recipe in their own, as for instance Quarkus has their own delegate.
That means it's likely safe to remove these indirections: anyone affected can use org.openrewrite.java.migrate.UpgradeJavaVersion directly with the appropriate version option.
Or better yet: Adopt the UpgradeToJavaXX recipes that go beyond just updating the build files and markers.
If we're not to adopt the recipe changes, then we should at least update the display names and descriptions the reflect that we change both Maven and Gradle build files, as well as source file markers.
These only delegate to
UpgradeJavaVersion
, but had adisplayName
anddescription
that were Maven specific, despite also updating Gradle build files, andSourceFile
Markers
after 9c6acfb5c5f2c942f8660a687b5263b3841c65ac.I'd say it's unlikely folks have specifically included these recipe in their own, as for instance Quarkus has their own delegate.
That means it's likely safe to remove these indirections: anyone affected can use
org.openrewrite.java.migrate.UpgradeJavaVersion
directly with the appropriateversion
option. Or better yet: Adopt the UpgradeToJavaXX recipes that go beyond just updating the build files and markers.