[
https://issues.apache.org/jira/browse/SUREFIRE-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778518#comment-15778518
]
Tibor Digana edited comment on SUREFIRE-1322 at 12/26/16 3:33 PM:
------------------------------------------------------------------
https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=303cc8acdaf677bee9751da94de16e07083febb7
was (Author: tibor17):
https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=9964119f3a238223e50b0bd6e813ea8dc03f910d
> Surefire and Failsafe should dump critical errors in dump file and console
> --------------------------------------------------------------------------
>
> Key: SUREFIRE-1322
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1322
> Project: Maven Surefire
> Issue Type: Bug
> Reporter: Tibor Digana
> Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
> Both plugins, Surefire and Failsafe, dump stack trace and error messages and
> lost commands in dump file or in console:
> [date]-jvmRun[N].dump,
> [date].dumpstream and
> [date]-jvmRun[N].dumpstream
> IN previous versions the plugins threw exceptions like,
> MojoExecutionException and MojoFailureException, but the user could not see
> any message of error which killed the plugin internally.
> Since now this is possible and the user can see the dump files in target
> target/failsafe-reports and target/surefire-reports.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
