maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Jefferson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1042) Provide way of running tests so that stack trace isn't dumped onto console
Date Thu, 10 Dec 2015 07:50:10 GMT

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

Andy Jefferson commented on SUREFIRE-1042:
------------------------------------------

It isn't about any parameter "being buggy". It's about changes introduced after 2.10 that
weren't backwards compatible (in a minor release!), and no apparent consideration being made
for people who want what it previously did.

> Provide way of running tests so that stack trace isn't dumped onto console
> --------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1042
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1042
>             Project: Maven Surefire
>          Issue Type: Bug
>    Affects Versions: 2.13, 2.14, 2.15, 2.16
>         Environment: Maven 3.x, Linux
>            Reporter: DN
>            Assignee: Tibor Digana
>         Attachments: test.zip
>
>
> We never used to get stack traces from any failed tests (asserts) being dumped onto the
console. "Upgrading" to 2.16 means that they now get dumped onto the console (UGLY IMHO).
Can we at least have the option of the previous output behaviour (2.10 for example)? If there
already is a way of achieving this, please advise, I couldn't find anything that had an effect.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message