[
https://issues.apache.org/jira/browse/SUREFIRE-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318217#comment-16318217
]
Réda Housni Alaoui commented on SUREFIRE-1457:
----------------------------------------------
[~tibor17], I understand that backward compatibility must be maintained between
minor versions.
But major versions are here to allow breaking changes.
IMO, the question is "Is it a bad default?", if yes it should be changed in the
next major version.
Otherwise, we can't touch anything and we are forced to keep bad things because
they have always been there?
I can't think of a better way to kill any software project.
Do we have to consider Maven as dead and move to gradle or other?
> 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
(v6.4.14#64029)
