You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2016/09/08 22:19:20 UTC
[jira] [Commented] (SUREFIRE-1277) Exceptions stacktrace in test
are limited to the test class in 2.19
[ https://issues.apache.org/jira/browse/SUREFIRE-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15475193#comment-15475193 ]
Tibor Digana commented on SUREFIRE-1277:
----------------------------------------
[~skygo]
Many people are asking this. The parameter {{trimStackTrace}} is and always was set to {{true}} by default.
In prior to 2.19 the behavior was not ok because it did not trim all non-test class in stack trace.
If you set it to {{false}}, you will see full log.
> Exceptions stacktrace in test are limited to the test class in 2.19
> --------------------------------------------------------------------
>
> Key: SUREFIRE-1277
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1277
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.19, 2.19.1
> Environment: Windows 10, java 8
> Reporter: Eric Barboni
> Assignee: Tibor Digana
> Attachments: surefiretest.zip
>
>
> Hi,
> Previous to 2.19, if an execption was raised in tested method the stacktrace contains trace from the test and tested method.
> Now the stacktrace contains only trace from test method, making it complicated to find the root cause.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)