> -----Original Message-----
> From: Paul Dillon [mailto:[EMAIL PROTECTED]]
> I'd prefer if it only printed the total transform time, or nothing at
> all, instead of:
[...]
> [junitreport] Transform time for package-summary.xsl: 100ms
Sorry garbage problem. Will be fixed indirectly.
> Also, it'd be fantastic if it worked with JAXP/Crimson, Xerces/Xalan1
> *and* Xerces/Xalan2 (I'm completely ignorant of how hard that
> might be).
API between Xalan 1 and Xalan 2 are very different and there were some
compatibility issues between the 2 that were not clear at the time of the
Ant release. Sorry about that. The next release should be much more
convenient for users.
> Seems like every man and his dog is including an XSL processor with
> their packages these days, and it's such a pain hunting them down. Or
> should I be directing this at the <style> task author?
No need to.
I cleaned up the way to generate the report and now makes use of the
redirect extension of xalan that allows multiple output from a single xsl
file. Having a single xsl file allows to use <style> task. So your problem
should be fixed indirectly. However if a processor requires a specific
parser at some point, there is not much I can do.
Thank a lot for your feedback !
--
Stephane Bailliez
Software Engineer, Paris - France
iMediation - http://www.imediation.com
Disclaimer: All the opinions expressed above are mine and not those from my
company.
