[
https://issues.apache.org/jira/browse/SUREFIRE-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744241#comment-16744241
]
Alon Bar-Lev commented on SUREFIRE-963:
---------------------------------------
Hi,
A voice from the future... :)
Actually... this <KEY/> notation should have produced a null value, hence,
remove the key out of environment... I landed on this bug because I am looking
for a way to unset environment variable during build... and differentiate
between empty and unset.
Thanks,
Alon
> Unable to set empty environment variables
> -----------------------------------------
>
> Key: SUREFIRE-963
> URL: https://issues.apache.org/jira/browse/SUREFIRE-963
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.13
> Environment: Linux Ubuntu 12.10,Maven 3.0.4
> Reporter: Christophe DENEUX
> Assignee: Tibor Digana
> Priority: Major
> Fix For: 2.18
>
> Attachments: SUREFIRE-963.txt
>
>
> With the following configuration of the maven-surefire-plugin:
> {code}
> <configuration>
> <environmentVariables>
> <PETALS_CLI_PREFS />
> </environmentVariables>
> </configuration>
> {code}
> I get the String "null" instead of "" as value of my env var in my unit test.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
