Re: [PR] [MRESOLVER-627] Improve transport selection and logging [maven-resolver]

2024-11-14 Thread via GitHub
cstamas merged PR #599: URL: https://github.com/apache/maven-resolver/pull/599 -- 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.

Re: [PR] [MRESOLVER-627] Improve transport selection and logging [maven-resolver]

2024-11-13 Thread via GitHub
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 rece

[PR] [MRESOLVER-627] Improve transport selection and logging [maven-resolver]

2024-11-13 Thread via GitHub
cstamas opened a new pull request, #599: URL: https://github.com/apache/maven-resolver/pull/599 In previous releases transport selection was really secretive and broken, as it considered invalid configuration as "protocol not supported" and Resolver did not log anything or worse, silently s