You can also do it just by specifying the class path to Saxon, too. Here's
one of my targets that does it:

<target name="make-xsds">
  <xslt basedir="Object meta-data" destdir="Object meta-data/xsd"
style="object-to-xsd.xsl" filenameparameter="filename" extension=".xsd">
   <classpath location="c:/saxon/saxon8.jar" />
  </xslt>
</target>

FWIW and HTH

Jay Bryant
Bryant Communication Services
http://www.bryantcs.com/

----- Original Message -----
From: "Robert Koberg" <rob@(protected)>
To: "Ant Users List" <user@(protected)>
Sent: Thursday, March 13, 2008 5:52 AM
Subject: Re: xslt version


> Currently, using XSLT version 2 means using Michael Kay's Saxon. You can
> get it from saxonica.com
>
> Put the saxon.jar on your classpath for the build and set the
> javax.xml.transform.TransformerFactory to use saxon. For example:
>
> <xslt in="a.xml" out="b.xml" style="c.xsl">
> <factory name="net.sf.saxon.TransformerFactoryImpl"/>
> </xslt>
>
> Or you could set a concrete subclass for the factory through a system
> property:
>
> javax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl
>
>
> On Thu, 2008-03-13 at 03:35 -0700, Z W wrote:
>> So how and where do I get a xslt 2.0 compliant processor to work with ant
>> 1.7 ?
>> Could someone explain how and where ?
>>
>> Thanks
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@(protected)
> For additional commands, e-mail: user-help@(protected)
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@(protected)
For additional commands, e-mail: user-help@(protected)