Re: [xsl] feasibility of HTML input

[Robert Koberg <rob@xxxxxxxxxx>]

didoss@xxxxxxxxxxx wrote:
> David -
>
> I was hoping not to interfere with the existing outputs,...I can go down that path if this one is not worthwhile.

Are you using Ant to generate reports? If so, you call a Tidy task (I 
think there is one) or create a class that calls it and use the java 
task. Then have another task that calls you summary report transform. It 
should be pretty simple as I am sure the respective reports are pretty 
uniform.

But, it would probably be better to output XML and use JUnit's and 
Emma's (?) XSL to transform to the report output. Then use the same XML 
to create you source. Then you don't need the tidy step.

best,
-Rob


> Dianne
>
>  -------------- Original message ----------------------
> From: David Wright <dave-xsl@xxxxxxxx>
>
> > 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