[ 
https://issues.apache.org/jira/browse/WAGON-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585069#comment-16585069
 ] 

Noel Grandin commented on WAGON-521:
------------------------------------

Yeah, that is my point, that java.net.useSystemProxies needs to be set to true 
"out of the box" so that Maven "just works" out of the box instead of failing 
after several minutes with a weird network error.

Perhaps the default installed mvn.cmd file needs to be updated?

Note that I'm not a user of maven in the sense of "using maven for my 
projects", I am a user of maven in the sense of "trying to get someone else's 
project that uses maven to work on my machine" so that it why I am trying to 
get this "fixed" in the default maven files

> Maven cannot use system default proxies
> ---------------------------------------
>
>                 Key: WAGON-521
>                 URL: https://issues.apache.org/jira/browse/WAGON-521
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-http
>    Affects Versions: 3.1.0
>         Environment: All
>            Reporter: Noel Grandin
>            Priority: Major
>
> when using maven from behind a proxy, it cannot connect to download
> The maven/java stuff will not use the system proxies unless explicitly told 
> to do so, which is a problem when maven tries to download the jars it needs 
> :-)
> Basically, I need the following option added to the java command line:
>     -Djava.net.useSystemProxies=true
> Sun did not see to make this the default because of backwards compatibility, 
> which is a right PITA, but anyhow :-)
> Please also see original issue here: 
> https://github.com/takari/maven-wrapper/issues/58
> https://github.com/pmd/pmd/issues/498



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to