If you have a java project that uses junit and you execute "gradle test" twice in a row
without any intervening call to 'clean' , then ant:junitreport complains that

TESTS-TestSuites.xml file is not a valide testsuite XML document

The first time though, everything runs fine, with no warning.

After tracking this down, it seems that the problem is on line 71 of

src/main/groovy/org/gradle/api/tasks/testing/AntJunit.groovy

In 0.5.2, it says:

fileset(dir: testResultsDir.absolutePath, includes: '*.xml')

Instead, I think it should probably say:

fileset(dir: testResultsDir.absolutePath, includes: '*.xml', excludes: 'TESTS-TestSuites.xml')

What I think is happening is that junitreport creates the TESTS-TestSuites.xml file on the
first execution, then sucks it in on the second, which is naughty.

I made this change on my own & things seem to work; that said, I'll leave it to someone else to
commit a change like this – I'm just coming back to gradle & don't have my sea legs yet.

The reason I kept this at 'major' is that I consider build-noise like this very dangerous
because it tends to obscure real problems and/or foster the "slum effect" when it comes
to warnings.

Incidentally, I checked off "patch submitted" in JIRA, but it's really just the 1-liner above.

Thanks again for Gradle!