You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2004/07/22 12:03:20 UTC
DO NOT REPLY [Bug 30254] New: -
xslt/style task not taking classpath into account
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30254>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30254
xslt/style task not taking classpath into account
Summary: xslt/style task not taking classpath into account
Product: Ant
Version: 1.6.1
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Core tasks
AssignedTo: dev@ant.apache.org
ReportedBy: xdury@hotmail.com
I'm willing to use a custom TransformerFactory (and a custom SAXParserFactory
which does implicit schema validation for default values) by specifying the new
classname into a file META-INF/services/javax.xml.transform.TransformerFactory
in the classpath... But the classpath attribute of xslt/style task doesn't take
this file into account, nor my custom transformerfactory .class file, nor the
libraries it needs like xalan (and xerces for the parserfactory).
Another problem is that my xsl often make use of calls to external classes to
do some controls, therefor I need to add those classes to the classpath, once
again the xslt/style task classpath attribute doesn't allow that...
Is it possible to make this classpath/classpathref attribute more global and
not just for specifying the factory to use? I don't see why it's so limited.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org