>Martijn Kruithof wrote:
>> Also can we be sure that project.createTask("xslt") always gives us
an
>> XSLTProcess?
>
>It would be nice to have
>XSLTProcess xsltTask = (XSLTProcess) project.create(XSLTProcess.class);
I dont see a problem with overloading project.create(String) with
project.create(
Antoine Levy-Lambert wrote:
1) do you agree that I submit the patch containing in the bug report
39708, rendering the XalanExecutor, Xalan1Executor, Xalan2Executor
classes useless and never called by our APIs.
+1
Martijn Kruithof wrote:
Also can we be sure that project.createTask("xslt") alwa
On Fri, 16 Jun 2006, Antoine Levy-Lambert <[EMAIL PROTECTED]> wrote:
> 1) do you agree that I submit the patch containing in the bug report
> 39708, rendering the XalanExecutor, Xalan1Executor, Xalan2Executor
> classes useless and never called by our APIs.
I didn't have the time to review it, but
Antoine Levy-Lambert schreef:
http://issues.apache.org/bugzilla/show_bug.cgi?id=39708
This patch renders the classes XalanExecutor, Xalan1Executor, Xalan2Executor in
the package org.apache.tools.ant.taskdefs.optional.junit useless.
So I have 2 questions :
1) do you agree that I submit the p
Hi,
I plan to apply the patches contained in the bug report submitted by Ivan
Ivanov, titled :
Modify task to support nested parameters that will be passed to
the underlying XSLT transformation
http://issues.apache.org/bugzilla/show_bug.cgi?id=39708
This patch renders the classes XalanExecu
