[
https://jira.codehaus.org/browse/SUREFIRE-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356150#comment-356150
]
Samuli Saarinen commented on SUREFIRE-649:
------------------------------------------
I stumbled to this as well when upgrading failsafe plugin. Our build also
relied on the behavior described by @afranken above. There really should be a
way to tackle this from maven/surefire side of things instead of using tricks
in application code. Maybe a switch to surefire/failsafe plugin to use the old
behavior if desired?
> 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)
