Paolo Castagna wrote:
Paolo Castagna wrote:
Hi,
I need to run a test suite which needs to connect to public web servers and
I am behind a web proxy.
I use:
mvn test -DproxyHost=... -DproxyPort=...
mvn test -DproxySet=true -DproxyHost=... -DproxyPort=...
Everything works fine with Maven v2.0.9 but with Maven v2.0.10 or v2.1.0
seems to me that the proxy does not get used.
I am probably missing something obvious...
I think the problem comes from the surefire plugin v2.4.3 used by Maven v2.0.10.
If I use the surefire plugin v2.4.2 I can see a lot of messages for system
properties, including:
[DEBUG] Setting system property [proxyHost]=[...]
[DEBUG] Setting system property [proxyPort]=[...]
This does not happen using the surefire plugin v2.4.3.
So, now, I forced v2.4.2 in my pom.xml:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.4.2</version>
[...]
</plugin>
Is this a known problem?
Yes, apparently this is a known BUG and it is not limited to proxyHost or
proxyPort
system properties... but, of course, is very bad for people who need to run test
suites behind a web proxy:
"This bug is preventing us from using 2.4.3, as we're running our tests behind
a proxy, i.e. ('mvn test -Dhttp.proxyHost=<proxyHost>
-Dhttp.proxyPort=<proxyPort>), and the system properties http.proxyHost and
http.proxyPort are being passed in as null. With 2.4.2, it works fine."
-- http://jira.codehaus.org/browse/SUREFIRE-121
Paolo
Paolo
Any help?
Paolo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
