-----Original Message-----
From: Steve Loughran [mailto:[EMAIL PROTECTED]
Sent: Monday, June 11, 2007 12:41 PM
To: Ant Users List
Subject: Re: Extending JUnit Ant tasks
Hi,
/*
well, sounds like you have to write a new xmllogger. One problem with a
streaming/flushing logger is that if the process died, the output is
still invald XML; the XSL engine would bail out.
*/
/*
yup, you're right. As our process uses the xmllogger only to present
the logfiles (not processed with xslt, just the raw xmllogfile) in a
browser
window, it would be no help, as browser would cough because of
invalid xml, but finally it's better than a 0 byte logfile.
*/
/*
Better to find out why your scripts are hanging and kill that. I always
timeout my exec/java and junit runs, and dont have to kill ant itself.
Have you tried that?
*/
hm, it's a generic worklflow that start ant scripts and waits for
reponse = Failed or Successful; as there are other jobs
in the queue you have to set a timeout to finish off a hanging job.
/*
The alternative is for ant to optionally register a signal handler (sun
java only; would cause trouble on IDEs) and then to shut down more
gracefully on termination.
*/
thanks for the pointer, i already have downloaded smartfrog 3.10.0000
but had no time to take a detailled look
/*
There is not yet any equivalent for the xmllogger, but it is something
that could be written if you want to help with it.
*/
i've found a contribution =
http://confluence.public.thoughtworks.org/display/CC/AntDirectXmlLogger
but =
: Direct XML Logger
call ant -listener org.apache.tools.ant.DirectXmlLogger
-DXmlLogger.file=Y:/antxmlout.xml -f %1
gives me a NullPointerException
i never wrote a logger for ant, maybe i try to write my own or fix the
DirectXmlLogger
when time allows
Regards, Gilbert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
