Resolver 2018 (#12112)#12133
Merged
Merged
Conversation
Bumps `resolverVersion` from 2.0.16 to 2.0.18. Also some related changes. Changes: * updates Resolver to 2.0.18 * dropped any existing filter building, is happening now in new component in Resolver 2.0.18 (same as in Maven 3.10.x) * user configured filter is NOT applied to plugin resolution * Legacy code uses `LegacyTrackingFileManager` the rest `TrackingFileManagerSupplier` * Expose `RepositorySystemSession` as session scoped, same as Maven 3.10.x (in fact, Maven 3.9.x did seed it, but Module by mistake never exposed it -- this is one of changes in Maven 3.10.x) Backport of ef8ae39
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Bumps
resolverVersionfrom 2.0.16 to 2.0.18. Also some related changes.Changes:
LegacyTrackingFileManagerthe restTrackingFileManagerSupplierRepositorySystemSessionas session scoped, same as Maven 3.10.x (in fact, Maven 3.9.x did seed it, but Module by mistake never exposed it -- this is one of changes in Maven 3.10.x)Backport of ef8ae39