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] [Closed] (SUREFIRE-1195) Add a feature to pass the proxy settings from the calling to the forked VM
Date Thu, 05 Nov 2015 16:46:27 GMT

     [ https://issues.apache.org/jira/browse/SUREFIRE-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tibor Digana closed SUREFIRE-1195.
----------------------------------
    Resolution: Not A Problem
      Assignee: Tibor Digana

Use this configuration
<properties>
 <myproxy>-Dhttp.proxyHost= ...</myproxy>
</properties>

plugin configuration:
<argLine>${myproxy}<argLine>

This is how to run with proxy:
mvn test

Without:
mvn test -Dmyproxy=

You may want to use <properties/> in two Maven profiles, withProxy and withoutProxy
proxy:
mvn -P withProxy test
mvn -P withoutProxy test

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

Mime
View raw message