Ken Wood <[EMAIL PROTECTED]> wrote: > Actually, this cuts to one of the Ant 1.2 requirements I want to > propose - and maybe it's already covered. The requirement is that > Ant provide a good API and VERY GOOD documentation on it's use so > that tasks don't have so much cut and pasted code scattered across > the tasks.
I think this is covered by >> * provide utility classes to aid in building tasks. ie like up-to-date >> functionality abstracted >> >> Need to become more specific here. > Another requirement, which I believe has been covered, but I'll > mention for insurance sake, is the ability to add new tasks to ant > by some type of 'drop in' or 'plug in' mechanism that is simple and > clean. Is on the list - and one of the features that I'm most certain of, that it will get approved. > Having to edit default.properties and re-build the jars just to get > a new task to appear built in is not ideal <taskdef>? Stefan
