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 Fri, 16 Nov 2001 11:00:32 GMT
On Fri, 16 Nov 2001 12:34, Tim Vernum wrote:
> From: Stefan Bodewig [mailto:bodewig@apache.org]
>
> > 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 should writing a task be a "bother".
> If it were trivial to write a CC task, then you should do it, because
> it clearly separates the declarations of 'what' to do, from the 'how'
> it is done.
>
> Buildfiles should say what.
> Tasks should say how.
>
> The problem is that right now it's easier to write the 'task' details in
> the buildfile, but it probably shouldn't be.

oooooh yer !

exactly my thoughts ;)

-- 
Cheers,

Pete

*------------------------------------------------------*
|  Hlade's Law: If you have a difficult task, give it  |
|     to a lazy person -- they will find an easier     |
|                    way to do it.                     |
*------------------------------------------------------*

--
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