[
https://issues.apache.org/jira/browse/SUREFIRE-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992146#comment-14992146
]
Michael Rumpf commented on SUREFIRE-1195:
-----------------------------------------
The global variables is a looonnng story. It is our corporate environment which
forces us to do such ugly things :(
I will try your myproxy suggestion and see how far I can get....
> Add a feature to pass the proxy settings from the calling to the forked VM
> --------------------------------------------------------------------------
>
> Key: SUREFIRE-1195
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1195
> Project: Maven Surefire
> Issue Type: Improvement
> Reporter: Michael Rumpf
> Assignee: Tibor Digana
>
> The proxy is configured in the user's settings.xml file.
> Unformately it seems as if there is not easy way to pass them to the child VM
> when the surefire plugin start the VM.
> The parameters
> * -Dhttp.proxyHost=${http.proxyHost}
> * -Dhttp.proxyPort=${http.proxyPort}
> * -Dhttps.proxyHost=${https.proxyHost}
> * -Dhttps.proxyPort=${https.proxyPort}
> * -Dhttp.nonProxyHosts=${http.nonProxyHosts}
> must only be passed to the forked VM when there are values. if the proxy is
> not configured and thus no values are present the parameters must not be
> passed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
