maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (Jira)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1195) Add a feature to pass the proxy settings from the calling to the forked VM
Date Thu, 30 Apr 2020 13:11:00 GMT

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

Tibor Digana commented on SUREFIRE-1195:
----------------------------------------

What i've see reused from the {{settings.xml}} was the {{servers id}} used in Maven Wildfly
Plugin, and this is okay because the maven resolver does not own this section. It is different
with the proxy, i would say.
Feel free to open a discussion at Maven mailinglist, https://maven.apache.org/mailing-lists.html

> 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)

Mime
View raw message