You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2018/01/06 22:24:00 UTC
[jira] [Commented] (SUREFIRE-1457) trimStackTrace should be
disabled by default
[ https://issues.apache.org/jira/browse/SUREFIRE-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16314962#comment-16314962 ]
Tibor Digana commented on SUREFIRE-1457:
----------------------------------------
[~reda-alaoui]
Sorry but breaking backwards compatibility cannot be made after years.
You have to get experiences with Maven. When you are going to use a new Maven plugin, you have to read documentation and a list of plugin goals and their configuration parameters.
> 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
> 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
(v6.4.14#64029)