Hi, I think this new task does not provide that much semanticaly unique capabilities to the existing 'execon', to justify existance of a seperate task. Maybe, 'execon' should have additional flag, like target set, which would trigger that time check? I would opt for expanding execon capabilities with this time-dependant check, and renaming it to <apply>.
If I think about it, all uses of execon (including changelog processing, idl compilation, html generation, etc) which I use it for now, would benefit from time target checking (do not generate Java sources if the .idl file is older, etc.), thus, I suspect execon would become obsolete after the new task will make its way to ant. I suggest making execon obolete, naming the new task 'apply', and adding there additional attribute for the target set. If the target set is not provided, apply will behave as old execon, if the target set is provided the time check will be performed. What about that? best regards Mariusz
