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

Lance Hankins <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |major

--- Comment #5 from Lance Hankins <[email protected]> ---
For what its worth - this seems like it should a higher priority bug, as it
will certainly prohibit anyone attempting to use Junit5 via <junitlauncher> and
<fork> from being successful. 

We just recently upgraded to Junit5 and then also had to upgrade to Ant 1.10.6,
so that we could use <fork> with <junitlauncher>.

We have configured: 

   <listener type="legacy-xml" sendSysOut="true" sendSysErr="true"/>

I spent much of the day trying to figure out why we get spurious extra
characters at the end of some of the generated JUnit results XML files.  For
our smallest module, we have about 90 tests (spread across 11 test classes) and
I was getting on average 2-4 corrupt XML files each time I ran all the tests in
this module (each corrupt file would have 1-2 extra characters after the last
XML tag, like "e>").   

This meant that <junitreport> would then complain about corrupt XML files when
it was trying to generate the HTML report, and then the affected test classes
would be left off of the HTML report, e.g. : 

   [junitreport] [Fatal Error] TEST-com.acme.CmdLineParserTest.xml:227:26:
Content is not allowed in trailing section.
   [junitreport] The file
/work/proj/build/test/data/TEST-com.acme.CmdLineParserTest.xml is not a valid
XML document. It is possibly corrupted.


I finally stumbled across this ticket and was very happy to see that Michael
had narrowed down the issue and submitted a fix (thanks Michael!)

That said - the fix hasn't made it to any released Ant distribution yet, so
anyone trying to use 1.10.6 in order to support JUnit5 with <fork> is likely
going to be banging their head on the same issue. 

I ended up doing the following in order to temporarily work around my issue
(hopefully with no ill side-effects): 
 1. pulled down the 1.10.7alpha nightly build (#1114 ) from:
https://builds.apache.org/job/Ant_Nightly/
 2. updated my 1.10.6 ant distribution to replace the original
lib/ant-junitlauncher.jar with the same jar from the nightly build

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

Reply via email to