maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (Jira)" <j...@apache.org>
Subject [jira] [Closed] (SUREFIRE-1781) Log a warning if forkCount = 0
Date Sat, 25 Apr 2020 18:54:00 GMT

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

Tibor Digana closed SUREFIRE-1781.
----------------------------------
      Assignee: Romain Manni-Bucau
    Resolution: Fixed

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

> Log a warning if forkCount = 0
> ------------------------------
>
>                 Key: SUREFIRE-1781
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1781
>             Project: Maven Surefire
>          Issue Type: Task
>            Reporter: Romain Manni-Bucau
>            Assignee: Romain Manni-Bucau
>            Priority: Trivial
>             Fix For: 3.0.0-M5
>
>
> Not forking for tests leads to unexpected behaviors and prevents some features (jpms,
system props, env) usage. Due to the fact forking is not that expensive now we should warn
about this (bad) practise.



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

Mime
View raw message