On 2010-08-12, tabber wrote:
> 1) You suggested 'another one would be to write your own task that wraps
> the exec invocation itself.' -- I am wondering what benefit it will be to do
> this?
A nicer syntax with less potential for errors.
Contrast the completely hypothetical
<mytests report="myfile.txt" spec="tests.spec"/>
with
<exec executable="mytests.sh">
<arg value="-o"/>
<arg file="myfile.txt"/>
<arg value="--spec"/>
<arg file="tests.spec"/>
</exec>
> 2) Currently our tests are run using a shell script on Linux/solaris boxes
> which are basically cron jobs. They dont run as soon as a build is
> completed. They run once every night on a build we assume will have been
> created by the time the cron triggers.
> If the output is not XML then can ANT understand the results at all?
It depends on what you want to do with them.
The <junitreport> task basically aggregates XML files and applies a
custom XSLT reansformation - this one expects a specific XML format. If
the output is not XML and you want to use <junitreport>, you will need
some sort of trasnformation step inbetween - which may just be a <copy>
or <concat> with some custim filterreader logic.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@ant.apache.org
For additional commands, e-mail: user-h...@ant.apache.org
