I asked because AFAIK we still haven't come to a decision regarding my "look it up from the antlib" DynamicElement hack in ConditionBase.
-Matt ----- Original Message ---- From: Peter Reilly <[EMAIL PROTECTED]> To: Ant Developers List <dev@ant.apache.org> Sent: Friday, September 29, 2006 12:30:52 PM Subject: Re: svn commit: r451000 - in /ant/core/trunk/src: main/org/apache/tools/ant/taskdefs/ main/org/apache/tools/ant/taskdefs/condition/ tests/junit/org/apache/tools/ant/ On 9/29/06, Matt Benson <[EMAIL PROTECTED]> wrote: > > Peter said: > > In ant 1.8, all conditions will be resolved by using void add(Condition > x), > > so tasks that want to have nested conditions just need to extend Task > and > > implement add(Condition x). > > Wait... how? With componentdef? Perhaps, the implementation does not matter, the important thing is that the api - add(Condition x) should "just work". Peter -Matt > > > > > Peter > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
