[
https://jira.codehaus.org/browse/SUREFIRE-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=307013#comment-307013
]
Kristian Rosenvold commented on SUREFIRE-867:
---------------------------------------------
The disadvantage of this strategy is that it creates a wholesale import of
unspecified environment variables to your project, which can effectively reduce
build reproducibility.
With the current system, the pom acts as an "interface specification" between
your build and the external environment, which means its possible to understand
which parameters will/can influence the build.
I will be proposing this as a wontfix.
> Add a way to declare all project properties as environmentVariables
> -------------------------------------------------------------------
>
> Key: SUREFIRE-867
> URL: https://jira.codehaus.org/browse/SUREFIRE-867
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
> Reporter: Pierre Le Roux
> Labels: proposed-wontfix
>
> It could be great to have a new option such as
> *allPropertiesAsEnvironmentVariables* (by default : false) that would
> retrieve all context properties (project, parent project and activated
> profile properties) and add it as environment variables.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
