when running cargo:redeploy targeting a remote container that is outside my network, cargo cannot resolve the host.
Failed to redeploy:
caused by: java.net.UnknownHostException: myserver.uk
It seems cargo ignores the proxy settings, either specified in settings.xml or passed via command line arguments -Dhttp.proxyHost etc. (which I find quite strange, since that should not happen, right?)
When I switch back to version 1.2.1 this problem does not occur. Here, cargo can connect to the server. In 1.2.1 however, CARGO-1042 Closed blocks my work.
- the full log to my command: mvn -s settings.xml cargo:redeploy -X -e -DskipTests -Dhttp.proxyHost=proxy -Dhttp.proxyPort=8080
- the settings.xml I use.
- a minimal example test case project, where I only anonymized server names and credentials.