[
https://issues.apache.org/jira/browse/SUREFIRE-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15518666#comment-15518666
]
Tibor Digana commented on SUREFIRE-1246:
----------------------------------------
The text of the documentation changed to:
{quote}
* Forked process is normally terminated without any significant delay
after given tests have completed.
* If the particular tests started non-daemon Thread(s), the process hangs
instead of been properly terminated
* by <em>System.exit()</em>. Use this parameter in order to determine the
timeout of terminating the process.
* <a
href="http://maven.apache.org/surefire/maven-surefire-plugin/examples/shutdown.html";>see
the documentation:
*
http://maven.apache.org/surefire/maven-surefire-plugin/examples/shutdown.html</a>
{quote}
> Surefire + Cobertura: Shutdown of Forked JVM timeouts before all thread ends
> ----------------------------------------------------------------------------
>
> Key: SUREFIRE-1246
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1246
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
> Affects Versions: 2.19.1
> Reporter: Ivo Pinheiro
> Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
> There should be a possibility to configure the Embedded shutdown timeout, to
> a value greater than 30 seconds.
> When using cobertura to evaluate the code coverage, and with a big number of
> tests to run, the surefire plugin does not wait for cobertura writes all
> cobertura information to cobertura.ser because the 30 seconds embedded
> shutdown timeout is not sufficient.
> Is it possible to add a configuration property to surefire-plugin to
> configure the embedded timeout time?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
