[
https://issues.apache.org/jira/browse/SUREFIRE-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16933716#comment-16933716
]
Benoit Lacelle commented on SUREFIRE-1457:
------------------------------------------
The root issue is well explained in
https://issues.apache.org/jira/browse/SUREFIRE-1226?focusedCommentId=16187391&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16187391
What many of us sees as a regression is considered a fix in 2.19. The "buggy"
behavior has been there from 2.13 to 2.18.1.
> trimStackTrace should be disabled by default
> --------------------------------------------
>
> Key: SUREFIRE-1457
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1457
> Project: Maven Surefire
> Issue Type: Improvement
> Reporter: Réda Housni Alaoui
> Assignee: Tibor Digana
> Priority: Critical
>
> We are using Jenkins at work.
> Each time we had test failures, stack trace were incomplete and therefore
> totally useless.
> I just discovered {{trimStackTrace}} option.
> IMO, the fact that this option is currently enabled by default is a total non
> sense.
> Now we have to change the pom.xml of every projects of the company to have a
> correct default.
> IMO, and I think I am not the only one here, trimStackTrace should be
> disabled by default.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
