Re: Using Java HTTP Client as the default HTTP transport

2025-11-14 Thread Tamás Cservenák
Just FYI, and sorry for the confusion, It was me hastily "demoting" but then after change in mind doing this: https://github.com/apache/maven-resolver/pull/1611 So, mvn4-rc-5 did NOT demote JDK transport after all. Still, this will not reduce deps as Martin writes, as HttpClient transport is still

Re: Using Java HTTP Client as the default HTTP transport

2025-11-14 Thread Matthias Bünger
This is what Open Source communities can achieve <3 Thank you very much Volkan (and ofc all others involved in any way)! Have a great weekend! Matthias Am 14.11.2025 um 13:29 schrieb Volkan Yazıcı: Hello, *Disclaimer: I am a member of the Apache Logging Services (Log4j, Log4cxx, Log4net) PMC

Re: Using Java HTTP Client as the default HTTP transport

2025-11-14 Thread Martin Desruisseaux
Hello Thanks Volkan for all this work, this is well appreciated. I'm not an expert in this part of Maven, but personally I would be happy to keep Java HTTP as the default mechanism. One of my medium-term wish, after Java module work, would be to reduce the number of Maven dependencies in the

Re: Using Java HTTP Client as the default HTTP transport

2025-11-14 Thread Christoph Läubrich
Hi Volkan, thanks for taking care of this, I likely will investigate and maybe "complain" a bit more about some of the things just wanted to share that for one project I now started to add "feature detection" like this so it degrades nicely on older JDK version (of course we hope everyone is