[EMAIL PROTECTED] wrote: > ... > - Because tasks in this context tend to be one-off, non-reusable bits > of code, it is > really nice to keep the task code in the same file as the rest of > the build.
I think that's a very important point. When you need to do something that's just a little more complex than is supported by regular tasks and features, it seems you shouldn't always have to deal with the bigger jump in complexity of breaking all the way out to writing an external class to implement a custom task. (Obviously, sometimes the external custom task is the right thing, but sometimes it probably isn't.) Daniel -- Daniel Barclay Digital Focus [EMAIL PROTECTED]
