[ https://issues.apache.org/jira/browse/MNG-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696623#comment-17696623 ]
Michael Osipov commented on MNG-7721: ------------------------------------- Solved by Wagon: https://github.com/apache/maven-wagon/blob/master/wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/AbstractHttpClientWagon.java#L557 > Maven 3.9 resolver ignores proxy configured via MAVEN_OPTS > ---------------------------------------------------------- > > Key: MNG-7721 > URL: https://issues.apache.org/jira/browse/MNG-7721 > Project: Maven > Issue Type: Bug > Components: Bootstrap & Build > Affects Versions: 3.9.0 > Reporter: Nejc Habjan > Priority: Major > > The new native resolver seems to no longer respect HTTP/S proxy configuration > set as JVM options via `MAVEN_OPTS`. I haven't tried if this also happens > when supplying the options directly via CLI as well, I assume that might be > the case? > Sample GitLab CI script that worked with 3.8.7 but now fails with 3.9: > {code:java} > image: maven:3.9 > build: > variables: > MAVEN_OPTS: >- > -Dhttp.proxyHost=$PROXY_HOST > -Dhttp.proxyPort=$PROXY_PORT > -Dhttps.proxyHost=$PROXY_HOST > -Dhttps.proxyPort=$PROXY_PORT > -Dhttp.nonProxyHosts=$NO_PROXY_HOSTS > script: > - mvn clean install{code} > Likely introduced in [https://github.com/apache/maven/pull/892]. -- This message was sent by Atlassian Jira (v8.20.10#820010)