Re: Setting Xalan to junitreport

On 8/29/07, J. David Beutel <[EMAIL PROTECTED]> wrote: > I haven't had much luck using XSLT 2 for junitreport. I think Saxon has > a problem with the redirect extension, which looks specific to Xalan. Indeed it is. You'll need to modify the .xsl to use Saxon instead of Xalan. XSL 2.0 supports ,

Re: Setting Xalan to junitreport

velopers List" Sent: Tuesday, August 28, 2007 9:44 AM Subject: Re: Setting Xalan to junitreport Stefan Bodewig wrote: Not using JDK 1.5's XSLTC is a good idea for so many reasons anyway. You could use the usual endorsed standards override mechanism[1] to swap in Saxon or just set the

Re: Setting Xalan to junitreport

in="${build.dir}/testresults/TESTS-TestSuites.xml" . Regards, Jan - Original Message - From: "J. David Beutel" <[EMAIL PROTECTED]> To: "Ant Developers List" Sent: Tuesday, August 28, 2007 9:44 AM Subject: Re: Setting Xalan to junitreport

Re: Setting Xalan to junitreport

Stefan Bodewig wrote: Not using JDK 1.5's XSLTC is a good idea for so many reasons anyway. You could use the usual endorsed standards override mechanism[1] to swap in Saxon or just set the system property javax.xml.transform.TransformerFactory prior to running Ant (you'd probably use the ANT_OPTS

Re: Setting Xalan to junitreport

On Mon, 27 Aug 2007, J. David Beutel <[EMAIL PROTECTED]> wrote: > Has there been any more action on this issue? Well, yes and no. delegates to under the covers (in 1.7) but you don't get access to the factory nested element. > I searched for junitreport in Bugzilla but didn't find it. I'm >

Re: Setting Xalan to junitreport

at, is that the point where its easiest to keep an eye on things - when there's a Bugzilla ticket to track? Thanks, Toby -Original Message- From: Antoine Levy-Lambert [mailto:[EMAIL PROTECTED] Sent: 12 June 2006 15:37 To: Ant Developers List Subject: Re: Re: Setting Xalan to jun

RE: Re: Setting Xalan to junitreport

+0100 Von: "Weston, Toby" <[EMAIL PROTECTED]> An: dev@ant.apache.org Betreff: Re: Setting Xalan to junitreport > Hi Guys, > > Sorry, been off list for a while, but does anyone know about any > progress on the following; > > http://marc.theaimsgroup.com/?l=

Re: Re: Setting Xalan to junitreport

Toby" <[EMAIL PROTECTED]> An: dev@ant.apache.org Betreff: Re: Setting Xalan to junitreport > Hi Guys, > > Sorry, been off list for a while, but does anyone know about any progress > on > the following; > > http://marc.theaimsgroup.com/?l=ant-dev&m=11471826

Re: Setting Xalan to junitreport

Hi Guys, Sorry, been off list for a while, but does anyone know about any progress on the following; http://marc.theaimsgroup.com/?l=ant-dev&m=114718268207732&w=2 It's regarding Antoine's comments on making junitreport use the xslt task (and so enable switching of XSLT engines). Thanks in advan

Re: Setting Xalan to junitreport / bug report 39407

I can see that in this case since the resource in question is unique to the task, it should be sufficient to assume that a nested resource is a stylesheet. The real requirement that will necessitate the attribute syntax, as I see it, is enforcing that a single resource be specified as the output d

Re: Setting Xalan to junitreport / bug report 39407

Matt, I plan to use the bug report : . which contains an attachment where the resource is instantiated using the URL schemes. I did not test it though to make sure that it does work with a jar:file: URL (not sure what the exact syntax i

Re: Setting Xalan to junitreport

Antoine: Does this put us back to needing a "scheme" to translate a string (attribute value) to a Resource? -Matt --- Antoine Levy-Lambert <[EMAIL PROTECTED]> wrote: > Hello Toby, > > it is not 100% straightforward. > > junitreport normally works by pulling the > stylesheets from ant.jar. >

Re: Setting Xalan to junitreport

Hello Toby, it is not 100% straightforward. junitreport normally works by pulling the stylesheets from ant.jar. The task normally only works with plain files as stylesheets. So I will first process a bug report showing how to use a resource as the stylesheet in the task. Afterwards, if th