On 2011-11-09, Steve Amerige wrote:
> Thanks for your reply. This won't work because the macrodef won't
> have any knowledge of what to do as per my need.
I have to trust you on that.
> I think, therefore, my solution of having 2 macrodef elements is as
> close as I can get:
>
> ...
> ...
>
Hi Stefan,
Thanks for your reply. This won't work because the macrodef won't have any knowledge of what to do as per my need. I think,
therefore, my solution of having 2 macrodef elements is as close as I can get:
...
...
So, then the question shifts a bit: in a macrodef, assuming that an
On 2011-11-08, Steve Amerige wrote:
> I'd like to do something like:
>
>
>
> ...
>
>
>
>...
>
> Within the macrodef, there would be places it would return true and
> other places it returns false. I want the solution to be wholly in
> Ant (no Java, Groo
Hi,
Thanks for the feedback. Actually, the use of Ant-Contrib is okay.
But, please note that it isn't just a property that I'd want to set. It's really the ability to look at the "return" values of a
macrodef and use that result with an task. I do realize that a workaround exists in this fo
Assuming no use of AntContrib, you can pass the name of a property to the
Macrodef, which it would set. This property could then be used in an Ant
condition. I'd give in and use AntContrib though, since it gives you an
task.
-Original Message-
From: Steve Amerige [mailto:steve.amer.