ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Rees <d.ree...@usa.net>
Subject Re: [VOTE] task/documentation writer's business
Date Tue, 27 Mar 2001 20:23:07 GMT

On Mon, 26 Mar 2001 09:02:07 -0500, Glenn McAllister wrote:

>Stefan Bodewig wrote:
>
>> Glenn McAllister <glenn@somanetworks.com> wrote:
>>
>> >> * Unify <available> and <uptodate> into a more general <condition>
>> >>   task, support AND/OR of several tests here.
>> >
>> > +0.  I guess we are getting pushed down that road.
>>
>> Well, the motivation behind this is quite clear - and I'm kind of
>> supporting it since I needed to check for JavaMail (which requires JAF
>> as well).
>>
>> The current way to do it (see JMeter's build file) involves two
>> targets with <available> tasks and looks silly, even if it works.
>>
>
>Don't get me wrong, I went through the same hoops as you, and I didn't
>like it either. :-)  I have to admit, this is probably one of the better
>compromises between the declaritive crowd and the procedural crowd.
>
>Having thought about it a little more, I'll upgrade my vote to a +1.
>


Making the change of available accepting a FileSet and FileSets
accepting cullers would handle all the available/uptodate combinations
involving files. Going further for more exotic tests is another
question...

d


Mime
View raw message