i know the eap and jws images are supposed to autoconfigure the maven proxy settings if HTTP_PROXY/HTTPS_PROXY is set, not sure why it's not working for you.
The problem is likely that HTTP_PROXY is uppercase, and not lowercase. See https://bugzilla.redhat.com/show_bug.cgi?id=1348945#c4
@martin: I don't think so, the middleware images have their own logic for how proxies are configured, as noted in comment 3, this isn't the curl problem.
Since image works well with it's special settings, remove the testblocker keyword > $HTTP_PROXY_HOST > $HTTP_PROXY_PORT > $HTTP_PROXY_USERNAME > $HTTP_PROXY_PASSWORD > $HTTP_PROXY_NONPROXYHOSTS
Lowering severity as there is viable workaround of using uppercase variables.
Closing this BZ. Work for this issue will continue on the linked JIRA - https://issues.jboss.org/browse/CLOUD-865.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days