Tamas Cservenak created MRESOLVER-627:
-----------------------------------------
Summary: Improve logging around transport selection
Key: MRESOLVER-627
URL: https://issues.apache.org/jira/browse/MRESOLVER-627
Project: Maven Resolver
Issue Type: Improvement
Components: Resolver
Affects Versions: 2.0.3
Reporter: Tamas Cservenak
Fix For: 2.0.4
Currently what transport is being used by Resolver is fully black box.
Examples:
* configure Maven 4 that by default would use JDK transport, create
{{.mvn/maven.config}} file with contents
{{-Daether.transport.jdk.httpVersion=HTTP_1_2}} (intentional typo). What
happens: Maven 4 will work but use Apache Transport.
* configure Maven 4 to use S3 transport but do not provide auth config. What
happens? Dependending on config, either some other transport will be selected
(and fail), or Resolver will tell "no available transport", which is untrue.
In both cases, Resolver config is bad, but:
* it is not reported anywhere
* in fact, it is silently ignored and Resolver continues like nothing happened
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
