Max Allan wrote:
> I cannot easily set the values in a settings.xml or elsewhere because the
> proxy host is always different for each build and the proxy settings are
> only needed in CICD, so adding them to settings would break local developer
> builds.
You could have a CI-specific settings fi
Sure, but Max cannot do that.
Will be done in 1.9.6: https://issues.apache.org/jira/browse/MRESOLVER-327
T
On Fri, Feb 24, 2023 at 8:39 AM Konrad Windszus wrote:
> Why not changing Native to call
> https://hc.apache.org/httpcomponents-client-4.5.x/current/httpclient/apidocs/org/apache/http/impl
Why not changing Native to call
https://hc.apache.org/httpcomponents-client-4.5.x/current/httpclient/apidocs/org/apache/http/impl/client/HttpClientBuilder.html#useSystemProperties()
by default (if nothing conflicting is explicitly configured)?
That way it would be more compatible with the Wagon i
Howdy,
Maven 3.9.0 changes default transport from Wagon to Native HTTP. Native
would respect proxy IF set in settings.xml, that as you explain, does not
fit your use case.
For now, with 3.9.0 you can fallback to Wagon using this
"-Dmaven.resolver.transport=wagon"
HTH
Tamas
On Fri, Feb 24, 2023
Hi,
I've got 2 separate maven builds configured like :
mvn clean install -Dhttps.proxyHost=$HTTPS_PROXY_HOST
-Dhttps.proxyPort=$HTTPS_PROXY_PORT -Dhttp.proxyHost=$HTTP_PROXY_HOST
-Dhttp.proxyPort=$HTTP_PROXY_PORT
That works fine on maven 3.8.7 but does not seem to even be trying to
connect to th
