[
https://jira.codehaus.org/browse/SUREFIRE-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356083#comment-356083
]
Arne Franken commented on SUREFIRE-649:
---------------------------------------
maybe this is a misunderstanding:
Before, when setting an empty SystemProperty <myproperty/>, Surefire would not
set that System Property at all for the forked process.
Now, the System Property is set with an empty value.
We actually want Surefire to ignore empty SystemProperty, just as
maven-tomcat-plugin does.
> Might be impossible to have empty strings in systemPropertyVariables element
> ----------------------------------------------------------------------------
>
> Key: SUREFIRE-649
> URL: https://jira.codehaus.org/browse/SUREFIRE-649
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.6
> Reporter: Laird Nelson
> Assignee: Tibor Digana
> Priority: Minor
> Fix For: 2.18
>
> Attachments: surefireEmptyStringIssue.tar.gz
>
>
> This stanza:
> <systemProperties>
> <property>
> <name>emptyProperty</name>
> <value></value>
> </property>
> </systemProperties>
> ...yields "" from System.getProperty("emptyProperty").
> This (supposedly better) stanza:
> <systemPropertyVariables>
> <emptyProperty></emptyProperty>
> </systemPropertyVariables>
> ...yields null from System.getProperty("emptyProperty").
> A test case is attached that demonstrates the issue.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
