I made a simple change to build.xml to separate out the junit HTML
report generation from junitreport which always ran junit-all.
The new target junit-html can be included as the last target in any
junit ant run to produce an HTML report of all the tests run in that ant
invocation.
E.g.
ant junit-clean junit-system-mini-codeline-jars junit-html
The HTML report is much easier to read and find the issues than the XML
files.
For me the report transformation that Derby does always fails, see
DERBY-2234 but the HTML report is generated correctly. Ie. it's readable
but doesn't include the Derby post-report formatting.
See:
http://wiki.apache.org/db-derby/DerbyTopLevelJunitTests#head-208e7a618585ecea93f5cfb35d85e78dd71bca60
Dan.
