You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tibor Digana (Jira)" <ji...@apache.org> on 2019/11/02 19:14:00 UTC

[jira] [Closed] (SUREFIRE-1705) new config parameter Exclude Environment Variables

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

Tibor Digana closed SUREFIRE-1705.
----------------------------------
    Resolution: Fixed

https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=80659dc49e8e480e9789baf033112fd66c5bc376

> new config parameter Exclude Environment Variables
> --------------------------------------------------
>
>                 Key: SUREFIRE-1705
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1705
>             Project: Maven Surefire
>          Issue Type: New Feature
>          Components: Maven Failsafe Plugin, Maven Surefire Plugin
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>            Priority: Major
>             Fix For: 3.0.0-M4
>
>
> Typically the Surefire JVM inherits environment variables from the parent process (Maven). You can specify environement variables (keys) in the configuration parameter 'excludedEnvironmentVariables' which excludes environment variables in the Surefire JVM.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)