On 9/29/06, Peter Reilly <[EMAIL PROTECTED]> wrote:
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
Or maybe we could implement a "mixin" method protocol:
void antMixin(ConditionBase x) {
this.condition = x;
}
This would be usefull for types/tasks that share common attributes but
do not want to use java's single inheratance to get the attributes/nested
elements.
For example the matches condition has regex attributes (singleline,
multiline, casesensitive),
pattern and nested regex. There could be given to a mixin class -
RegexMixin,
this could be shared with other types/tasks.
void antMixin(RegexMixin x) {
this.regexParams = x;
}
Peter
"just work".
Peter
-Matt
>
> >
> > Peter
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
