maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SUREFIRE-1457) trimStackTrace should be disabled by default
Date Tue, 29 May 2018 09:57:00 GMT

    [ https://issues.apache.org/jira/browse/SUREFIRE-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493318#comment-16493318
] 

Mark Struberg edited comment on SUREFIRE-1457 at 5/29/18 9:56 AM:
------------------------------------------------------------------

+1 to disable it and go back to the original behaviour (which means to print all the stack
trace as it was in maven 1, 2 and earlier in maven 3 days). 


was (Author: struberg):
+1 to disable it and go back to the original behaviour. 

> 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)

Mime
View raw message