[
https://issues.apache.org/jira/browse/MNG-8560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923915#comment-17923915
]
Noel Grandin commented on MNG-8560:
-----------------------------------
Never mind, this is apparently a known Java issue where it treats any proxy
settings as meaning "use SOCKS" which lead to it getting stuck when connecting
to my proxy server
> Maven wrapper does not obey the configured maven proxies
> --------------------------------------------------------
>
> Key: MNG-8560
> URL: https://issues.apache.org/jira/browse/MNG-8560
> Project: Maven
> Issue Type: Bug
> Components: Maven Wrapper
> Affects Versions: 3.0-alpha-1
> Reporter: Noel Grandin
> Priority: Major
>
> As it says, if I try and run mvnw from my command line, it won't use the
> configured proxies.
> Not the ones in settings.xml
> Not the ones configured via the well-known HTTPS_PROXY environment variable.
> Not the ones configured in my Windows Control Panel.
> Originally reported here [https://github.com/takari/maven-wrapper/issues/58]
> Generally, using maven from behind a proxy is a bad experience
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
