[
https://issues.apache.org/jira/browse/SUREFIRE-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187549#comment-16187549
]
Tibor Digana commented on SUREFIRE-1226:
----------------------------------------
[~Srdo]
I will think about where we can put the hint [1] in order to workaround this
issue. Placing the hint after every test error would be annoying seen
everywhere almost the same and therefore it should be in one place in the
summary, maybe in the end.
Another option would be to display top stack trace classes with same package
like the test class has but then the parameter would have to be {{String}} and
not {{boolean}}. We already have such principle in {{debugForkedProcess}} which
can be {{true|false}} or JVM debug switch.
[1]: 5 stack frames elided, set trimStackTrace=false to display
> 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
> Assignee: Tibor Digana
> 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.4.14#64029)