We just made some mods to the JUnit task in the current source (1.5 alpha) that does stack trace filtering for error and failure output for the xml. plain and basic formatters. For that reason and because I've never seen this particular problem you're having, I'd suggest trying a nightly build from yesterday or today. At least upgrade to 1.4.1. We've been using 1.5 alphas for months at work.
Best, Scott Stirling Framingham, MA > -----Original Message----- > From: Steve Madsen [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 11, 2001 6:40 PM > To: [EMAIL PROTECTED] > Subject: JUnit XML formatter corruption > > > When running a suite of unit tests on Solaris (Ant 1.4), I see the > following error when <JUnitReport> is run: > > [junitreport] The file <...> is not a valid XML document. It is possibly > corrupted. > > Looking in the file reveals an extra ">" character at the very end, on a > line by itself. This does not happen when running the same test suite > on Windows 2000 (Ant 1.4). > > I've looked in the mailing list archives, scoured Google and read > through the code. I can't for the life of me see how this could happen. > > Does this behavior ring a bell with anyone? > > -- > Steve Madsen <[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
