Add validation to `ChangeDependency`, so it checks that either group or artifact is different from the old.

What problem are you trying to solve?

the Change*Dependency… recipes are specifically for changing to a different dependency (as the name implies, doh!). The fact that it has a newVersion parameter tripped me up. I see UpgradeDependencyVersion does what I expected. A reference from Change… to Upgrade may be helpful. In fact I see Change… being used supposedly to perform an upgrade (judging from the recipe docs) when perhaps an Upgrade… was intended. If the old and the new G+A are identical and newVersion is specified, then it's not a move/change and likely should be an Upgrade.

Describe the solution you'd like

Add validation to ChangeDependency, so it checks that either group or artifact is different from the old. This would apply to both the rewrite-java-dependency recipe, as well as the two rewrite-maven recipes.

Have you considered any alternatives or workarounds?

use a yaml rewrite recipe to change existing recipies (like the ones above) to use Upgrade if the new and old G+A are the same. use a yaml rewrite recipe to change existing recipies (like the ones above) to use Upgrade if the new and old G+A are the same.

Additional context

As suggested on OSS Slack by @tobli

openrewrite / rewrite-java-dependencies

Add validation to `ChangeDependency`, so it checks that either group or artifact is different from the old. #55

What problem are you trying to solve?

Describe the solution you'd like

Have you considered any alternatives or workarounds?

Additional context