ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 29596] New: - XSLT task ignores classpath element/attribute when looking up transformer
Date Wed, 16 Jun 2004 10:50:56 GMT
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: dev@ant.apache.org
        ReportedBy: jez@jezuk.co.uk


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: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message