[SUREFIRE-1772] Suppressed exceptions not shown in trimmed stack trace

**[Jörg Sautter](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=joerg1985)** opened **[SUREFIRE-1772](https://issues.apache.org/jira/browse/SUREFIRE-1772?redirect=false)** and commented

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)

---

**Affects:** 3.0.0-M4

**Issue Links:**
- [SUREFIRE-1432](https://issues.apache.org/jira/browse/SUREFIRE-1432) trimStackTrace = false by default

1 votes, 4 watchers

Start in the Maven Surefire plugin's trimmed stack-trace reporting path and review the behavior described by SUREFIRE-1432. Verify how failures with suppressed exceptions are rendered when trimStackTrace is enabled, then use the existing reporting tests or add coverage to confirm that suppressed exceptions appear in console output.

Written by the indexing model from the issue text.