ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Diane Holt <hol...@yahoo.com>
Subject Re: Overriding the default XSLT processor w/o using CLASSPATH
Date Fri, 03 May 2002 19:21:37 GMT
--- Russ Freeman <russ@freesoft.co.uk> wrote:
> Since hearing that I don't need to setup CLASSPATH before call my Ant
> script with a <style> task, I've since tried to use the <classpath>
> element to specify the location of a xalan install without success,
> i.e:-
> 
> <style 
> 	in="${component.root}/Test/Scratch/testresults.xml"
> 	extension="html"
> 	style="${components.root}/Build/Code/Scripts/testresults.xsl"
> 	out="${build}/testresults.html">
> 	<classpath>
> 		<pathelement location="${xalan.api}/bin/xalan.jar"/> 
> 		<pathelement location="${xalan.api}/bin/xml-apis.jar"/> 
> 		<pathelement
> location="${xalan.api}/bin/xercesImpl.jar"/> 
> 	</classpath>
> </style> 
> 
> No matter what I try the style task seems unable to see the XSLT
> processor. It works if I setup CLASSPATH beforehand though.

Have you tried also setting the 'processor' attribute (see the Parameters
table)?  (I've never used this task, so I'm not sure if you're supposed to
need it or not when specifying the classpath inside the task, but it seems
it couldn't hurt to give it a try.)

Diane

=====
(holtdl@yahoo.com)



__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com

--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>


Mime
View raw message