[MNG-7608] Make native transport the default #892
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
This immediately cuts in "half" the count of HTTP requests against Maven Central or any major MRM. Altering the meaning of "default": is now same as "auto", but still leaving it in place for future, as "default" at some point may again become something different than "native". --- https://issues.apache.org/jira/browse/MNG-7608
gnodet
approved these changes
Dec 2, 2022
|
This PR needs more |
kwin
approved these changes
Dec 2, 2022
rmannibucau
approved these changes
Dec 2, 2022
|
before this it was possible for users to use their own wagon impls. |
|
Nothing of legacy is lost, resolver transport (since Maven 3.0) was always like this: All what happened here is the "transport-wagon" got it's original priority for resolver applied (is demoted). Hence, to use custom wagon, all you need is to set transport-wagon, and from there, everything is "as before". This change merely exposed (and reordered) the first level of "transort-*" nodes... |
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.
This immediately cuts in "half" the count of HTTP requests against Maven Central or any major MRM.
Altering the meaning of "default": is now same as "auto", but still leaving it in place for future, as "default" at some point may again become something different than "native".
https://issues.apache.org/jira/browse/MNG-7608