Dianne,
If it is possible to have JUnit and Emma produce XML and you do not want
to interfere with your existing outputs, why don't you create both HTML
and XML from your existing tools. That way you'll have your reports in
both formats.
------------------------------------------
Jerry Kimmel - jkimmel at vasont dot com
-----Original Message-----
From: didoss(_at_)comcast(_dot_)net [mailto:didoss(_at_)comcast(_dot_)net]
Sent: Friday, March 17, 2006 1:06 PM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] feasibility of HTML input
David -
I was hoping not to interfere with the existing outputs,...I can go down
that path if this one is not worthwhile.
Dianne
-------------- Original message ----------------------
From: David Wright <dave-xsl(_at_)dexy(_dot_)org>
I'm a bit puzzled - a quick google suggests that it isn't hard to get
both
JUnit and Emma to produce XML reports, as well as HTML. You'd be much
better off parsing that, than the user-friendly HTML. Is there a
reason
why you can't?
Cheers,
David Wright
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--