[
https://issues.apache.org/jira/browse/SUREFIRE-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493372#comment-16493372
]
Tibor Digana commented on SUREFIRE-1457:
----------------------------------------
We will finish version 2.22.0 where we implement JUnit5. After this release
we do not want to prolong 2.x anymore and jump to 3.0 release candidate.
There we have a chance to alter behavior.
On Tue, May 29, 2018 at 11:57 AM, Mark Struberg (JIRA) <[email protected]>
> trimStackTrace should be disabled by default
> --------------------------------------------
>
> Key: SUREFIRE-1457
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1457
> Project: Maven Surefire
> Issue Type: Improvement
> Affects Versions: 2.21.2
> 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
(v7.6.3#76005)
