[
https://issues.apache.org/jira/browse/SUREFIRE-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148933#comment-15148933
]
John Vines edited comment on SUREFIRE-1029 at 2/16/16 5:18 PM:
---------------------------------------------------------------
Is there an explanation for why this isn't a problem? Or for tracking that
trimStackTrace (what I'm guessing is your suggested workaround) more useful due
to the issues Andrew mentioned
was (Author: vines):
Is there an explanation for why this isn't a problem?
> Report suppressed exceptions
> ----------------------------
>
> Key: SUREFIRE-1029
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1029
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
> Affects Versions: 2.15, 2.16
> Reporter: Andrew Gaul
> Attachments: AutoCloseableMain.java, AutoCloseableTest.java
>
>
> Surefire only reports the exception from a try-with-resources body, not any
> suppressed exceptions from close methods. I see this behavior from the
> attached AutoCloseableMain.java:
> {code}
> Exception in thread "main" java.io.IOException: from body
> at AutoCloseableMain.main(AutoCloseableMain.java:9)
> Suppressed: java.io.IOException: from close
> at ThrowIOExceptionOnClose.close(AutoCloseableMain.java:17)
> at AutoCloseableMain.main(AutoCloseableMain.java:10)
> {code}
> I see a different behavior from the attached AutoCloseableTest.java:
> {code}
> java.io.IOException: from body
> at
> com.maginatics.AutoCloseableTest.testAutoCloseable(AutoCloseableTest.java:14)
> {code}
> Surefire could call Throwable.getSuppressed via reflection to maintain
> compatibility with earlier versions of Java. Refer to Guava Closer which
> does something similar.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
