[Smartfrog-checkins] [Smartfrog.org-JIRA] Commented: (SFOS-839) TerminationRecord.toString() should include the stack trace of all nested exceptions

[Steve L. (JIRA) <ji...@sm...>]

    [ http://jira.smartfrog.org/jira/browse/SFOS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11492#action_11492 ] 

Steve Loughran commented on SFOS-839:
-------------------------------------

Or the test runner should grab any attached exceptions and log them. That keeps the toString() terse but makes the junit logs useful

> TerminationRecord.toString() should include the stack trace of all nested exceptions
> ------------------------------------------------------------------------------------
>
>                 Key: SFOS-839
>                 URL: http://jira.smartfrog.org/jira/browse/SFOS-839
>             Project: SmartFrog
>          Issue Type: Improvement
>          Components: .sfCore
>    Affects Versions: 3.12.040
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>             Fix For: 3.17.x
>
>
> uncommitted enhancements to the testing framework cause early startup failures to get turned into termination records and propagated back to the caller -but now the termination record doesn't print the full stack trace
> TerminationRecord.toString() should do so

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.smartfrog.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira