You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lukas Theussl (JIRA)" <ji...@codehaus.org> on 2006/03/29 02:52:45 UTC
[jira] Updated: (MPJUNITREPORT-11) Keep nested exceptions in
truncated stack traces
[ http://jira.codehaus.org/browse/MPJUNITREPORT-11?page=all ]
Lukas Theussl updated MPJUNITREPORT-11:
---------------------------------------
Fix Version: 1.5.1
> Keep nested exceptions in truncated stack traces
> ------------------------------------------------
>
> Key: MPJUNITREPORT-11
> URL: http://jira.codehaus.org/browse/MPJUNITREPORT-11
> Project: maven-junitreport-plugin
> Type: Improvement
> Environment: linux/windows with jdk 1.4/1.5
> Reporter: Cyrille Le Clerc
> Priority: Minor
> Fix For: 1.5.1
> Attachments: junit-report-test.zip, junit-report.diff
>
> Original Estimate: 30 minutes
> Remaining: 30 minutes
>
> IMPROVEMENT DESCRIPTION
> =======================
> JUnit Report truncate stack traces after 'at org.apache.commons.jelly.tags.ant.AntTag.doTag' or 'at sun.reflect.NativeMethodAccessorImpl.invoke0(' to remove org.maven.* and org.apache.jakrta.jelly.* lines.
> However, the drawback is that it removes the stack trace of nested exceptions ("Caused by ...").
> This is due to the call of a method that is not able to split exceptions and preserve nested stack traces "stringTool.splitStringAtLastDelim(stringTool.splitStringAtLastDelim(failure.text, 'at org.apache.commons.jelly.tags.ant.AntTag.doTag').get(0)".
> Here is a contribution that keeps nested stack traces.
> MODIFIED / ADDED FILES
> ====================
> - junit.jsl : call ExceptionTool instead of StringTool
> - ExceptionTool.java and ExceptionToolTest.java : java util class to split and truncate exception stack traces. These files are declared under the package org.maven.plugins.junitreport
> - project.xml : add junit-3.8.1.jar dependency
> - junit-report-test.zip is a sample. See the improvement in junit-report.html.
--
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