ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Benson <>
Subject Seeking feedback on possible macrodef augmentation
Date Tue, 26 Sep 2006 15:41:41 GMT
It strikes me that we don't have a utility to
declaratively build custom conditions from others;
macrodef would seem the obvious choice for, e.g.:

<macrodef name="isEmptyFile">
  <attribute name="file" />
      <available file="@{file}" type="file" />
      <length file="@{file}" length="0" />

But the result amounts to a Task: executable, but
unavailable for use where conditions would be

Would it make sense to allow this by allowing a nested
<condition> as an alternative to <sequential>?  Then
cloning the MacroInstance class to MacroCondition
implements Condition, for use when <condition> is
specified?  Cloning the entire MacroDef/MacroInstance
family to have an entirely new task feels a little
extreme to me here...

Alternative suggestions?


Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message