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=29596>. 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=29596 XSLT task ignores classpath element/attribute when looking up transformer Summary: XSLT task ignores classpath element/attribute when looking up transformer Product: Ant Version: 1.6.1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Ant manual for XSLT task says classpath the classpath to use when looking up the XSLT processor. The XSLT task uses the defined classpath to look up the XSLTLiason class. Historically, this made sense. Now, Trax is standard and the XSL:P and Xalan liasons are deprecated. It would seem to make sense to allow the TraXLiason to use the defined classpath to look up the transformer to use. The factory element allows you to specify the precise transformer class to use, but if that class isn't on the default classpath you're sunk. If TraXLiason could use the XSLTProcess' classpath, you can ship your processor of choice in your build configuration and the problem is solved. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
