You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2015/09/06 22:45:06 UTC

[jira] [Closed] (SUREFIRE-783) A boolean option to push all maven props to system props

     [ https://issues.apache.org/jira/browse/SUREFIRE-783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed SUREFIRE-783.
-----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> A boolean option to push all maven props to system props
> --------------------------------------------------------
>
>                 Key: SUREFIRE-783
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-783
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: process forking
>    Affects Versions: 2.10
>            Reporter: Benson Margulies
>
> I'd like to implement an idea, but only if the serious sure-fire-ists agree.
> At my shop, people constantly expect that setting a Maven property will produce a -D for them in tests, and they have to be taught, over and over, the contrary.
> Parallel to a feature of antrun, I propose to make an option to make it trivial to make surefire match such expectations. If this option is true, all the maven properties from the pom, plus the same list of 'common' global props from antrun, would be turned into system property values.
> I'm a committer I'll take care of this if there are no objections.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)