At 02:59 14/6/00 -0400, you wrote: >This has me intrigued. I do not believe it is as simple as moving this >code from init to execute. The trouble is that Ant constructs instances of >all the tasks up front (calling init as it goes), then goes off and >executes them. Defering the taskdef to execute means that the new tasks >will not be defined in time.
uggg this I didn't know. Is there any reason that objects are created at the begining instead of as targets are executed ? Ease of implementation ? >An alternative would be to allow taskdefs to be deferred as an option. >What that would do instead of creating the "real" task is to create a >instance of a new class, say "proxyTask". This task would be special and >would simply accumulate the attributes, as well as being passed the name of >the real task. When it comes time to execute this task, it would attempt >to create an instance of the real task, apply all the attributes, and >finally invoke init followed by execute. seems like a very large work around ... Cheers, Pete *------------------------------------------------------* | "Nearly all men can stand adversity, but if you want | | to test a man's character, give him power." | | -Abraham Lincoln | *------------------------------------------------------*
