Use default resolver in MillAlg
#3234
Merged
Conversation
This file contains 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
... instead of hardcoding Maven Central. If the default resolver is not overridden it, it will be Maven Central, so nothing will change in this case. I'm doing this for the same reason as given in #1899 where the hardcoded Maven Central was replaced in `SbtAlg` with the default resolver.
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #3234 +/- ##
==========================================
- Coverage 91.06% 91.06% -0.01%
==========================================
Files 163 163
Lines 3391 3390 -1
Branches 308 304 -4
==========================================
- Hits 3088 3087 -1
Misses 303 303 ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
... instead of hardcoding Maven Central. If the default resolver is not overridden it, it will be Maven Central, so nothing will change in this case.
I'm doing this for the same reason as given in #1899 where the hardcoded Maven Central was replaced in
SbtAlgwith the default resolver.