ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: ResourceCollections
Date Mon, 11 Apr 2005 09:45:40 GMT
On Thu, 07 Apr 2005, Peter Reilly <> wrote:

> We should be able to make all the current conditions, selectors and
> filters be typedefs.


> There are only a few name over-laps:
>    and, or, not  (selectors and conditions)

and we need to solve them - there will be more to come, in particular
more plaggable things where boolean combinations will make sense.  An
<or> that can be used as condition or selector simply won't scale

What is the alternative to placing the typedefs corresponding to the
different versions of <or> into separate antlibs?  roles?


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

View raw message