From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
> 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. > Stefan > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > The information contained in this email is confidential. If you are not the intended recipient, you may not disclose or use the information in this email in any way. Macquarie Bank does not guarantee the integrity of any emails or attached files. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
