Linkage Monitor to work with repositories that hosts other BOMs than google-cloud-bom #1156
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
elharo
approved these changes
Jan 27, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes #1154 .
Problem to solve
Before this PR, Linkage Monitor does not check the updated BOM in a repository. Suppose Linkage Monitor is setup for https://github.com/googleapis/google-auth-library-java. It ignores any new change in the google-auth-library-bom.
How to solve
Maven's model builder provides API
modelRequest.setModelResolver(ModelResolver modelResolver), where we can intercept model resolution. This PR leverages the API by introducingVersionSubstitutingModelResolverwhich substitutes the versions of specified Maven coordinates.