junitreport generates incorrect output when run w/ AntRunner [message #310091] |
Mon, 20 November 2006 16:45  |
Eclipse User |
|
|
|
The junitreport ANT task is based on an xslt that makes stacktrace output
readable by replacing newlines with <br> tags. When junitreport is invoked
by AntRunner, the newlines are not replaced w/ <br> and appear to be deleted
completely.
I suspect this is due to the fact that the template calls extension
functions as in:
<xsl:template name="br-replace">
<xsl:param name="word"/>
<xsl:param name="br"><br/></xsl:param>
<xsl:value-of select='stringutils:replace(string($word),"
",$br)'/ >
</xsl:template>
the stringutils package is declared at the top of the template as:
xmlns:stringutils="xalan://org.apache.tools.ant.util.StringUtils"
but it does not appear to be processed.
I'm not expert here, so perhaps someone can give a hint as to what is not
configured correctly?
Or perhaps this is candidate for a bug report?
Thanks
Michael Giroux
|
|
|
|
|
|
Re: junitreport generates incorrect output when run w/ AntRunner [message #310460 is a reply to message #310091] |
Mon, 04 December 2006 13:00  |
Eclipse User |
|
|
|
With some research, I have discovered that the problem is not related to
using AntRunner.
"Michael Giroux" <michael.giroux@bull.com> wrote in message
news:ejt7l9$on4$1@utils.eclipse.org...
> The junitreport ANT task is based on an xslt that makes stacktrace output
> readable by replacing newlines with <br> tags. When junitreport is
> invoked by AntRunner, the newlines are not replaced w/ <br> and appear to
> be deleted completely.
>
> I suspect this is due to the fact that the template calls extension
> functions as in:
> <xsl:template name="br-replace">
> <xsl:param name="word"/>
> <xsl:param name="br"><br/></xsl:param>
> <xsl:value-of select='stringutils:replace(string($word),"
",$br)'/ >
> </xsl:template>
The replace function is acting as if there is not replacement string and the
NL is being deleted completely.
I have changed the value of param br to other strings, and these are all
injected into the text, so it seems the problem has to do with the
definition of the replacement value.
I'll go off to the xalan mailing list to ask about this.
Michael
|
|
|
Powered by
FUDForum. Page generated in 0.03927 seconds