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 2017/05/04 15:25:04 UTC

[jira] [Closed] (SUREFIRE-1364) Report XML should contain system properties of forked JVM

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

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

https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=4e993a05460ef72e17a39a6e9edf9e0ef402859f

> Report XML should contain system properties of forked JVM
> ---------------------------------------------------------
>
>                 Key: SUREFIRE-1364
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1364
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Failsafe Plugin, Maven Surefire Plugin
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>             Fix For: 2.20.1
>
>
> Currently testing in forked JVM means that report XML contains system properties of Maven process.
> Each test class executed in forked JVM should emit system properties of that JVM on startup.
> In-Plugin process (forkCount=0 or forkMode=never) should again keep own properties of master process.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)