[
https://issues.apache.org/jira/browse/SUREFIRE-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744683#comment-16744683
]
Alon Bar-Lev commented on SUREFIRE-963:
---------------------------------------
> If you find the problematic line in code
The problem is not with the code but the implementation... we should be able to
diffrenciate between unset environment variable and set it to empty, the <X/>
notation is good for unset as java gets null and not empty string. Now it is
too late as it will break backward compatibility, so I opened SUREFIRE-1624. If
you tell me what notation should be, I can try and work this out.
> 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)
