[
https://issues.apache.org/jira/browse/SUREFIRE-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189572#comment-17189572
]
Jesse Glick commented on SUREFIRE-1798:
---------------------------------------
bq. pushing this change right now would mean that the behavior of configuration
parameter would change. We have a big opportunity to use the version 3.0.0-M5
in Maven 3.7.0.
Misleading I think. From what I can tell, the current default version in Maven
is 2.12.4, which did trim stack traces by default but only above the test code:
in the above example, lines below {{BaseSlackIntegrationTest.setUp}}. (The
trimming actually seems to be broken in 2.12.4 at least on JUnit 4.13; fixed in
2.13.) Still potentially missing some critical diagnostic information, but far
less likely than the current (2.19+) behavior.
Therefore I would advise against such an upgrade until this issue is fixed, as
it would make everyday test-driven development less usable by default.
> trimStackTrace should be false by default
> -----------------------------------------
>
> Key: SUREFIRE-1798
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1798
> Project: Maven Surefire
> Issue Type: Task
> Components: Maven Surefire Plugin
> Reporter: Romain Manni-Bucau
> Priority: Major
>
> True was intended to clean up the output but it always misses any useful data
> so let's set an useful default
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
