Message: The following issue has been closed.
Resolver: Jason van Zyl Date: Sat, 28 Jun 2003 8:06 AM We are not using DVSL anymore. --------------------------------------------------------------------- View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-147 Here is an overview of the issue: --------------------------------------------------------------------- Key: MAVEN-147 Summary: DVSL to xdoc to HTML problem with < and > Type: Bug Status: Closed Priority: Major Resolution: WON'T FIX Time Spent: Unknown Estimate: 0 minutes Project: maven Versions: 1.0-beta-7 Assignee: Jason van Zyl Reporter: Vincent Massol Created: Fri, 1 Nov 2002 2:15 PM Updated: Sat, 28 Jun 2003 8:06 AM Description: Hi, I have a test case that fails and thus the error is: "Expected <xxxx> but was <yyyy>" This is stored in the junit XML report as: <error message="expected:<SELECT...> but was:<null>" [...] But when it goes throught the first DVSL transformation to transform it into a valid xdoc, it is translated to: <code> junit.framework.ComparisonFailure: expected:<SELECT...> but was:<null> [...] And then xdoc:transform transforms it into HTML : <code> junit.framework.ComparisonFailure: expected:<SELECT...> but was:<null> [...] And the browser just simply ignore these unknown tags and displays: "junit.framework.ComparisonFailure: expected: but was: at " [...] How to correct? Thanks -Vincent --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]