[
https://issues.apache.org/jira/browse/SUREFIRE-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17095758#comment-17095758
]
Tibor Digana commented on SUREFIRE-1195:
----------------------------------------
That's what i am say that the proxy defined in the settings.xml has totally
different purpose. It is used for the Dependencies Resolver to be able to
download the artifacts. Normally it is Nexus server of JFrog Repo. But here in
these test it is the INT infrastructure which may have no relation to repo
proxy. It is no guarantee that every company has the same infrastructure. Even
there may be an intended integration test as a component test intentionally
testing the HTTP server in Failsafe sandbox and still no relation to the proxy
in settings.xml.
> 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
> Priority: Major
>
> 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
(v8.3.4#803005)
