https://bz.apache.org/bugzilla/show_bug.cgi?id=65030

            Bug ID: 65030
           Summary: LegacyXmlResultFormatter fails when properties contain
                    illegal XML characters
           Product: Ant
           Version: 1.10.8
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Optional Tasks
          Assignee: notifications@ant.apache.org
          Reporter: dominik.stad...@gmx.at
  Target Milestone: ---

When system properties contain some control characters, e.g. "ESC", ASCII 0x1b,
the resulting XML file is invalid and thus producing the test-report fails:

test-main:
    [javac] Compiling 1 source file to /tmp/git-svn/build/classes
    [javac] Support for javac --release has been added in Java9 ignoring it
    [mkdir] Created dir: /tmp/git-svn/build/dist/maven/poi
      [jar] Building jar:
/tmp/git-svn/build/dist/maven/poi/poi-5.0.0-SNAPSHOT.jar
    [javac] Compiling 1 source file to /tmp/git-svn/build/test-classes
    [javac] Support for javac --release has been added in Java9 ignoring it
      [jar] Building jar:
/tmp/git-svn/build/dist/maven/poi-tests/poi-5.0.0-SNAPSHOT-tests.jar
    [mkdir] Created dir: /tmp/git-svn/build/report
[junitreport] [Fatal Error] TEST-org.apache.poi.TestPOIDocumentMain.xml:1:826:
Ungültiges XML-Zeichen (Unicode: 0x1b) wurde im Wert des Attributs "value"
gefunden. Element ist "property".
[junitreport] The file
/tmp/git-svn/build/test-results/TEST-org.apache.poi.TestPOIDocumentMain.xml is
not a valid XML document. It is possibly corrupted.
[junitreport] Processing /tmp/git-svn/build/report/TESTS-TestSuites.xml to
/tmp/null1284078419
[junitreport] Loading stylesheet
jar:file:/opt/apache/apache-ant/apache-ant-1.10.9/lib/ant-junit.jar!/org/apache/tools/ant/taskdefs/optional/junit/xsl/junit-frames.xsl
[junitreport] Transform time: 321ms
[junitreport] Deleting: /tmp/null1284078419
     [echo] Published results from tests at build/report/index.html


It seems the XMLReportWriter should apply the same logic as the one from JUnit
5 itself received via this PR https://github.com/junit-team/junit5/pull/2275

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to