Skip Invalid Transitive Dependency When Resolving Maven Dependencies

[XiaoSK]

What problem are you trying to solve?

When applying a Recipe (such as OrderImports) to a Maven project, during the execution of the rewrite-maven-plugin plugin, if an undefined version of a transitive dependency is encountered due to an irregular pom.xml of a dependency, the plugin will fail with a "No version provided" error.

Describe the solution you'd like

In fact, under Maven's default build behavior, Maven merely issues a warning: “[WARNING] The POM for groupId:artifactId:packing:version is invalid, transitive dependencies (if any) will not be available” without blocking the build process. Such irregular pom.xml files are indicative of technical debt, and the goal of OpenRewrite is to eliminate this technical debt. However, I believe that during the execution of the rewrite-maven-plugin, it should align with Maven’s default behavior by issuing only warnings and ignoring the transitive dependencies instead of blocking the execution. At the very least, the plugin should provide an optional Maven argument to allow ignoring and skipping such cases.

This would enhance the plugin's compatibility, allowing it to work more seamlessly with a wider range of projects that may have varying levels of technical debt or dependency management issues. By providing this flexibility, users can choose to bypass non-critical errors without compromising the overall build process, thus improving the robustness and adaptability of the plugin in different environments.