This would be a beautiful feature to have. It adds so
much power without adding much complexity.

How would you handle the vocabulary of the test
attribute of condition? Would you allow extensions of
conditions, or what?

John

--- Peter Donald <donaldp@apache.org> wrote:
> Hi,
> 
> I was just talking with someone about the prospect
> of filesets with 
> cullers/filters etc and they pointed out n
> interesting thing. This same 
> problem was "solved" in SQL years ago. ie imagine
> the following is psuedo 
> antified sql. This would allow us to perform all the
> complex things that 
> people have asked for but simply. 
> 
> Select */*.java from src/java where readable == true
> 
> 
> So you would have 
> 
> Select NAME-PATTERN from BASE-DIRECTORY where
> CONDITIONS
> 
> In ant1 out filesets already have the capability of
> representing
> Select NAME-PATTERN from BASE-DIRECTORY. It would be
> simple to extend this 
> with a where clause. As a consequence of looking at
> this way I thought it 
> could be represented fairly easily by a minor change
> such as
> 
> <include name="**/*.java">
>   <condition test="..." />
>   <condition test="..." />
>   <condition test="..." />
> </include>
> 
> Thoughts?
> 
> Cheers,
> 
> Pete
> 
>
*-----------------------------------------------------*
> | "Faced with the choice between changing one's
> mind, |
> | and proving that there is no need to do so -
> almost |
> | everyone gets busy on the proof."                 
>  |
> |              - John Kenneth Galbraith             
>  |
>
*-----------------------------------------------------*


=====
John Casey

jdcasey@digitalsymbiosis.net
Omni CodeWorks, Inc.

__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/