ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Donald <dona...@apache.org>
Subject Re: [PATCH] ant task with (nested) fileset(s)
Date Mon, 12 Nov 2001 11:55:18 GMT
On Mon, 12 Nov 2001 22:46, Stefan Bodewig wrote:
> On Mon, 12 Nov 2001, Peter Donald <donaldp@apache.org> wrote:
> > On Mon, 12 Nov 2001 22:03, Stefan Bodewig wrote:
> >> but if my project contains three or four C files for my JNI stuff
> >> and the simple <apply> task is all I need, then why should I bother
> >> writing a task for it?
> >
> > why not?
>
> For the same reasons I use <exec> or <java> for one shot things.  I
> don't need a custom task that goes beyond the stuff that is already
> there, because my use case is to simple.
>
> Without <apply>, I'd have to write a silly combination of three
> targets, an <uptodate> task, a property and an <exec> task for all
> three C sources - here I'd start to think about a custom task.
>
> With <apply>, all I need is there and this task is just putting
> together some pieces that are part of Ant's support library.

Is this based on the assumption that writing tasks is as hard as it is now ? 

-- 
Cheers,

Pete

-----------------------------------------------------
First, we shape our tools, thereafter, they shape us.
-----------------------------------------------------

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message