[
http://jira.codehaus.org/browse/SUREFIRE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144682#action_144682
]
Brett Porter commented on SUREFIRE-511:
---------------------------------------
right... I actually prefer the second format so it'd be a good switch, but OTOH
changing it just to workaround what is probably a Maven bug (since it should
know to toString() values as they are populated) feels a bit wrong.
> Proposal to use java Map for surefire's systemProperties
> ---------------------------------------------------------
>
> Key: SUREFIRE-511
> URL: http://jira.codehaus.org/browse/SUREFIRE-511
> Project: Maven Surefire
> Issue Type: Improvement
> Components: plugin
> Affects Versions: 2.4.3
> Reporter: Dan Tran
> Attachments: SUREFIRE-511.patch
>
>
> There is a known problem documented at
> http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html
> where maven properties other than java String are not able to pass into
> surefire
> This is mainly because systemProperties is mapped to java Properties class.
> However if we map it to java Map
> the problem solves.
> see
> http://svn.codehaus.org/mojo/trunk/mojo/build-helper-maven-plugin/src/it/surefire
> for details.
> So I would like to propose that we deprecate "systemProperties" and introduce
> a new one "systemPropertyVariables" to use java Map ( similar to surefire's
> environmentVariables"
> Thoughts?
--
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
