Add combined FindRepositoryOrder for Maven and Gradle #171
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
org.openrewrite.java.dependencies.FindRepositoryOrderthat delegates to both Maven and GradleFindRepositoryOrderrecipesMavenRepositoryOrderdata table withid,uri,knownToExist, andrankfor projects using either build systemProblem
Users running
FindRepositoryOrderagainst organizations with mixed Maven and Gradle projects had to run the Maven and Gradle recipes separately. Gradle-only orgs got no results from the Maven recipe.Solution
A combined recipe following the same pattern as
FindDependency,ChangeDependency, etc. — delegates to the build-system-specific implementations viaisAcceptable().Dependencies
org.openrewrite.gradle.search.FindRepositoryOrder. This PR will not compile until that PR is merged and released.Test plan