ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 19118] New: - JUnitReport does not fail when it encounters an invalid XML file
Date Thu, 17 Apr 2003 16:59:38 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19118>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19118

JUnitReport does not fail when it encounters an invalid XML file

           Summary: JUnitReport does not fail when it encounters an invalid
                    XML file
           Product: Ant
           Version: 1.5.3
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Optional Tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: goetze@dovetail.com
                CC: bl7385@momail.sbc.com


Currently the JUnitReport task only logs a warning if it encounters an invalid 
XML file (see the SAXException catch clause in the createDocument method in 
XMLResultAggregator).  As written, it is impossible to check for this condition 
within an Ant script.  Bug 19113 describes a case where the JUnit task can 
produce an invalid XML output file.

One possibility would be to support an errorproperty parameter (like the one 
one the JUnit task) that gets set if an error occurs.

Another choice (a little less flexible) would be to support a "failOnError" 
parameter.

Mime
View raw message