[MRESOLVER-440] Clean up transport names and config keys #375
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
|
Doco is not yet updated... |
michael-o
requested changes
Nov 21, 2023
...lver-transport-apache/src/main/java/org/eclipse/aether/transport/apache/HttpTransporter.java
Outdated
Show resolved
Hide resolved
cstamas
changed the title
sschuberth
pushed a commit
to oss-review-toolkit/ort
that referenced
this pull request
Jul 6, 2024
Note that `maven-resolver-transport-http` has been renamed to `maven-resolver-transport-apache`, see [1]. [1]: apache/maven-resolver#375
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.
Clean up transport names, also fix problem (historical) where config is related to "connector", as these are since then "transports" and there is one connector provided OOTB in resolver. Finally, solve documentation for config properties.
Along actual cleanup, class and transport renames and key renames, all the config properties have been documented (mostly using javadoc) and also a "tool" has been implemented that can be used to generate configuration reference page, so no more manual authoring needed.
https://issues.apache.org/jira/browse/MRESOLVER-440