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 2020/04/13 23:29:00 UTC
[jira] [Commented] (SUREFIRE-1772) Suppressed exceptions not shown
in trimmed stack trace
[ https://issues.apache.org/jira/browse/SUREFIRE-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082739#comment-17082739 ]
Tibor Digana commented on SUREFIRE-1772:
----------------------------------------
[~joerg1985]
The Opensource allows you to provide a fix.
Feel free to open the pullrequest on GitHub and ping us and we will help you.
> Suppressed exceptions not shown in trimmed stack trace
> ------------------------------------------------------
>
> Key: SUREFIRE-1772
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1772
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 3.0.0-M4
> Reporter: Jörg Sautter
> Priority: Major
>
> Suppressed exceptions are not shown in the console output of the maven plugin, this has been reported as #SUREFIRE-1029 before. It was rejected in the past due to the expected Java sourcecode 1.6 expected in Maven 3.0 and suppressed execptions are a 1.7 feature.
> Maven 3 actually uses java 1.7 as minimum and this could be implemented now.
> Additionally more frameworks are using the suppressed exceptions feature and a the lack in reporting is more important than in the past, e.g. [JUnit5 is using suppressed exceptions|https://github.com/junit-team/junit5/issues/1602#issuecomment-427305459]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)