You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Fabulich (JIRA)" <ji...@codehaus.org> on 2007/11/24 09:53:57 UTC
[jira] Closed: (SUREFIRE-166) trimStackTrace=true trims "caused
by:" sections complelely away
[ http://jira.codehaus.org/browse/SUREFIRE-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Fabulich closed SUREFIRE-166.
---------------------------------
Resolution: Fixed
fixed in revision 597825. I believe some earlier check-ins had sort of fixed this, but then broke trimming altogether for many stacktraces.
> trimStackTrace=true trims "caused by:" sections complelely away
> ---------------------------------------------------------------
>
> Key: SUREFIRE-166
> URL: http://jira.codehaus.org/browse/SUREFIRE-166
> Project: Maven Surefire
> Issue Type: Bug
> Reporter: Tuomas Kiviaho
> Priority: Minor
> Fix For: 2.4
>
>
> Description of the parameter 'trimStackTrace' states "trim the stack trace in the reports to just the lines within the test" which it does nicely on the stacktrace, but there may be additional information in the initial cause that doesn't fall to the category "not within the test". Without trimming these "caused by:" lines of course show up, but so does the overly long test framework part of the stacktrace.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira