cstamas commented on PR #599: URL: https://github.com/apache/maven-resolver/pull/599#issuecomment-2474774728
> I don't have an opinion on this. Sure, no problem. But let me explain what was initial cause for this PR: We knew that JDK transport cannot handle HTTP/2 `GOAWAY`, and recently we saw a surge in ITs and other jobs getting it, so we decided to _force_ HTTP/1.1 while keeping JDK transport in use. I did that by creating `.mvn/maven.config` in maven and mvnd projects... then I went to check "effects" using `-X` locally and was **very surprised to see that Maven started using Apache transporter instead**. Basically, turned out my config had wrong value (a typo), and even `-X` did not report this, instead all I saw in debug logs is that Maven uses Apache transport.... turned out, this typo was interpreted as "not my protocol" by JDK transport, and it made Maven select next available HTTP Transporter that was Apache. Very confusing. Hence, this PR now: * logs every transport "disqualification" (in DEBUG) instead only when no transport could be selected * fails the build if any transport is mis-configured -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
