>Steve Loughran wrote:
>
>Take the XSL stylesheets that junit report uses and rework them to
meet your needs.
>
Thanks Steve -- I'm not sure if this will solve my problem completely,
although it may be a good temporary fix.
I want to reduce the number of exception lines in the results XML fi
I am running some JUnit tests through Ant's junit task, and I am hoping
to be able to filter out most of the exceptions which are currently
displayed in the failure reports. I have set filtertrace="on", but this
appears to be the default and it makes no difference. Essentially I
just want the
Thanks for the heads up Matt.
Actually this does appear to be an Eclipse problem, as
I can run the target from the command line without
getting the missing file error.
--James
>
> To quickly eliminate Eclipse from the list of
> suspects, can you successfully execute the build
from
> the comma
I am executing an Ant target which worked well a few
days ago, and now it complains that a file isn't
found. I can see the file in the directory tree so I
know it's there. Other Ant targets in the same
build.xml are working fine. I'm not sure if this is a
problem with Ant or with the task being run
