You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Renaud Julienne (JIRA)" <ji...@codehaus.org> on 2007/03/13 16:35:34 UTC
[jira] Created: (SUREFIRE-308) Setting environment variables in
surefire configuration overwrite the existing environment
Setting environment variables in surefire configuration overwrite the existing environment
------------------------------------------------------------------------------------------
Key: SUREFIRE-308
URL: http://jira.codehaus.org/browse/SUREFIRE-308
Project: Maven Surefire
Issue Type: Bug
Components: plugin
Affects Versions: 2.3, 2.0 (2.2 plugin)
Environment: Linux
Reporter: Renaud Julienne
It's possible to set additional environment properties in surefire plugin configuration using:
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<environmentVariables>
<NAME>value</NAME>
</environmentVariables>
</configuration>
</plugin>
As described in plugin documentation, this should ADD the environment variable NAME to the existing environment when forking to launch the tests.
What happens in fact is that it completely OVERWRITE the existing environment as soon as you use this configuration property : no more $HOME, no more $PATH, etc... Whereas when this property is not set, the existing environment ($HOME, $PATH, ...) remains present.
This is not critical as there is a workaround to still have $HOME or $PATH for example by setting:
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<environmentVariables>
<NAME>value</NAME>
<HOME>${env.HOME}</HOME>
<PATH>${env.PATH}</PATH>
</environmentVariables>
</configuration>
</plugin>
but afaic, this remains a high issue.
I did not have time to investigate much, but it seems the problem comes from org.codehaus.plexus.util.cli.CommandLine, so this bug may be also opened there.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SUREFIRE-308) Setting environment variables in
surefire configuration overwrite the existing environment
Posted by "Dan Fabulich (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Fabulich closed SUREFIRE-308.
---------------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: 2.x)
Can't reproduce in latest 2.4 trunk; integration test checked in.
> Setting environment variables in surefire configuration overwrite the existing environment
> ------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-308
> URL: http://jira.codehaus.org/browse/SUREFIRE-308
> Project: Maven Surefire
> Issue Type: Bug
> Components: plugin
> Affects Versions: 2.0 (2.2 plugin), 2.3
> Environment: Linux
> Reporter: Renaud Julienne
>
> It's possible to set additional environment properties in surefire plugin configuration using:
> <plugin>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <environmentVariables>
> <NAME>value</NAME>
> </environmentVariables>
> </configuration>
> </plugin>
> As described in plugin documentation, this should ADD the environment variable NAME to the existing environment when forking to launch the tests.
> What happens in fact is that it completely OVERWRITE the existing environment as soon as you use this configuration property : no more $HOME, no more $PATH, etc... Whereas when this property is not set, the existing environment ($HOME, $PATH, ...) remains present.
> This is not critical as there is a workaround to still have $HOME or $PATH for example by setting:
> <plugin>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <environmentVariables>
> <NAME>value</NAME>
> <HOME>${env.HOME}</HOME>
> <PATH>${env.PATH}</PATH>
> </environmentVariables>
> </configuration>
> </plugin>
> but afaic, this remains a high issue.
> I did not have time to investigate much, but it seems the problem comes from org.codehaus.plexus.util.cli.CommandLine, so this bug may be also opened there.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-308) Setting environment variables in
surefire configuration overwrite the existing environment
Posted by "Dan Tran (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103456 ]
Dan Tran commented on SUREFIRE-308:
-----------------------------------
plexus-utils-1.4.3 fixes this issue I think.
> Setting environment variables in surefire configuration overwrite the existing environment
> ------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-308
> URL: http://jira.codehaus.org/browse/SUREFIRE-308
> Project: Maven Surefire
> Issue Type: Bug
> Components: plugin
> Affects Versions: 2.0 (2.2 plugin), 2.3
> Environment: Linux
> Reporter: Renaud Julienne
>
> It's possible to set additional environment properties in surefire plugin configuration using:
> <plugin>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <environmentVariables>
> <NAME>value</NAME>
> </environmentVariables>
> </configuration>
> </plugin>
> As described in plugin documentation, this should ADD the environment variable NAME to the existing environment when forking to launch the tests.
> What happens in fact is that it completely OVERWRITE the existing environment as soon as you use this configuration property : no more $HOME, no more $PATH, etc... Whereas when this property is not set, the existing environment ($HOME, $PATH, ...) remains present.
> This is not critical as there is a workaround to still have $HOME or $PATH for example by setting:
> <plugin>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <environmentVariables>
> <NAME>value</NAME>
> <HOME>${env.HOME}</HOME>
> <PATH>${env.PATH}</PATH>
> </environmentVariables>
> </configuration>
> </plugin>
> but afaic, this remains a high issue.
> I did not have time to investigate much, but it seems the problem comes from org.codehaus.plexus.util.cli.CommandLine, so this bug may be also opened there.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-308) Setting environment variables in
surefire configuration overwrite the existing environment
Posted by "Tim Hay (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136759#action_136759 ]
Tim Hay commented on SUREFIRE-308:
----------------------------------
Even though this is closed, it's I think it's still worth commenting on, considering the extreme difficulty I had finding out what the problem was in the first place, given the errors I was experiencing (see stacktrace below)
Dan's comment above is correct. In a Windows XP environment, I found that when an <environmentVariables> element was added to the configuration for version 2.3 of the surefire plugin, all other environment variables were from then on unavailable. In particular, the SYSTEM_ROOT variable, required when using apache CXF. In this situation, we would get the following stacktrace:
30/05/2008 15:49:37 org.apache.cxf.phase.PhaseInterceptorChain doIntercept
INFO: Interceptor has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Unrecognized Windows Sockets error: 10106: create
at org.apache.cxf.interceptor.AbstractOutDatabindingInterceptor.writeParts(AbstractOutDatabindingInterceptor.java:77)
at org.apache.cxf.interceptor.BareOutInterceptor.handleMessage(BareOutInterceptor.java:68)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:221)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:276)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:222)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:177)
at $Proxy56.getUsernameList(Unknown Source)
at com.suncorp.jpetstore.api.service.account.AccountServiceSoapJmsIntegrationTest.shouldProxyGetUsernameList(AccountServiceSoapJmsIntegrationTest.java:37)
There are two ways to work around this:
1) Override the dependency surefire has on plexus-utils, such that it explicitly depends on version 1.4.3.
2) Update to the latest version of the Surefire Plugin - which at time of writing is 2.4.3.
Obviously, option 2 is preferred.
The following details relevant environment information:
Windows XP 5.1
Java: jdk 1.6.0_06
Maven v2.0.7 (and then upgraded to v2.0.9)
> Setting environment variables in surefire configuration overwrite the existing environment
> ------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-308
> URL: http://jira.codehaus.org/browse/SUREFIRE-308
> Project: Maven Surefire
> Issue Type: Bug
> Components: plugin
> Affects Versions: 2.0 (2.2 plugin), 2.3
> Environment: Linux
> Reporter: Renaud Julienne
>
> It's possible to set additional environment properties in surefire plugin configuration using:
> <plugin>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <environmentVariables>
> <NAME>value</NAME>
> </environmentVariables>
> </configuration>
> </plugin>
> As described in plugin documentation, this should ADD the environment variable NAME to the existing environment when forking to launch the tests.
> What happens in fact is that it completely OVERWRITE the existing environment as soon as you use this configuration property : no more $HOME, no more $PATH, etc... Whereas when this property is not set, the existing environment ($HOME, $PATH, ...) remains present.
> This is not critical as there is a workaround to still have $HOME or $PATH for example by setting:
> <plugin>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <environmentVariables>
> <NAME>value</NAME>
> <HOME>${env.HOME}</HOME>
> <PATH>${env.PATH}</PATH>
> </environmentVariables>
> </configuration>
> </plugin>
> but afaic, this remains a high issue.
> I did not have time to investigate much, but it seems the problem comes from org.codehaus.plexus.util.cli.CommandLine, so this bug may be also opened there.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-308) Setting environment variables in
surefire configuration overwrite the existing environment
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated SUREFIRE-308:
----------------------------------
Fix Version/s: 2.x
> Setting environment variables in surefire configuration overwrite the existing environment
> ------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-308
> URL: http://jira.codehaus.org/browse/SUREFIRE-308
> Project: Maven Surefire
> Issue Type: Bug
> Components: plugin
> Affects Versions: 2.0 (2.2 plugin), 2.3
> Environment: Linux
> Reporter: Renaud Julienne
> Fix For: 2.x
>
>
> It's possible to set additional environment properties in surefire plugin configuration using:
> <plugin>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <environmentVariables>
> <NAME>value</NAME>
> </environmentVariables>
> </configuration>
> </plugin>
> As described in plugin documentation, this should ADD the environment variable NAME to the existing environment when forking to launch the tests.
> What happens in fact is that it completely OVERWRITE the existing environment as soon as you use this configuration property : no more $HOME, no more $PATH, etc... Whereas when this property is not set, the existing environment ($HOME, $PATH, ...) remains present.
> This is not critical as there is a workaround to still have $HOME or $PATH for example by setting:
> <plugin>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <environmentVariables>
> <NAME>value</NAME>
> <HOME>${env.HOME}</HOME>
> <PATH>${env.PATH}</PATH>
> </environmentVariables>
> </configuration>
> </plugin>
> but afaic, this remains a high issue.
> I did not have time to investigate much, but it seems the problem comes from org.codehaus.plexus.util.cli.CommandLine, so this bug may be also opened there.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira