Perfect solution, thanks! --that was the patch that
mimics the original behavior, right?
-Matt
--- Peter Reilly [EMAIL PROTECTED] wrote:
Opps, you are correct.
I was using my anti-xml-hell patch
http://marc.theaimsgroup.com/?l=ant-devm=107763945224538w=2
you need to do the following
Opps, you are correct.
I was using my anti-xml-hell patch
http://marc.theaimsgroup.com/?l=ant-devm=107763945224538w=2
you need to do the following silliness:
antlib
presetdef name=myls xmlns:c=ant:current
apply executable=ls
c:arg value=-l/
/apply
/presetdef
/antlib
see:
That should work, at least it does for me:
presetdef name=myls
apply executable=ls
arg value=-l/
/apply
/presetdef
in an antlib at package test
and used:
project xmlns:t=antlib:test
t:myls
t:fileset dir=./
/t:myls
/project
Matt Benson wrote:
I am finding that I cannot define
I can't figure it out... I am using your exact example
and I get The antlib:test:myls type doesn't support
the nested arg element
-Matt
--- Peter Reilly [EMAIL PROTECTED] wrote:
That should work, at least it does for me:
presetdef name=myls
apply executable=ls
arg value=-l/
I am finding that I cannot define the following in an
antlib:
presetdef name=myexecutable
apply executable=myexecutable
arg value=-f /
/apply
/presetdef
and reference it with a namespace, due to the fact
that the nested elements keep the default namespace,
even using the myexecutable
