[
https://issues.apache.org/jira/browse/SUREFIRE-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140710#comment-15140710
]
Tibor Digana edited comment on SUREFIRE-1226 at 2/10/16 12:40 PM:
------------------------------------------------------------------
This is exactly controversal because some users argued against the behavior you
want to have now. Some users are irritated to see long stack. We did not
discuss it whether to trim it before/after test method, we did in whole stack.
This could be maybe an extension point in the Version 3.0.
We will release several release candidates but the first one should be 3.0
compatible and we will introduce extensions API. The most important extension
is the Test List Processor which will be released first.
was (Author: tibor17):
This is exactly controversal because some users argued against the behavior you
want to have now. Some users are irritated to see long stack. We did not
discuss it whether to strim it before/after test method, we did in whole stack.
This could be maybe an extension point in the Version 3.0.
We will release several release candidates but the first one should be 3.0
compatible and we will introduce extensions API. The most important extension
is the Test List Processor which will be released first.
> Surefire trims all stack trace elements except those in the test that failed
> ----------------------------------------------------------------------------
>
> Key: SUREFIRE-1226
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1226
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.19
> Reporter: Jiri Locker
> Priority: Minor
> Attachments: mvn_stacktrace.tar.gz
>
>
> This looks like a re-occurrence of SUREFIRE-992 but now the stack trace is
> even more trimmed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
