maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Kasnacheev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1457) trimStackTrace should be disabled by default
Date Thu, 12 Apr 2018 12:08:00 GMT

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

Ilya Kasnacheev commented on SUREFIRE-1457:
-------------------------------------------

This default makes exactly zero sense. Please change it in the next major.

> 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