I could suggest a more generic name like <apply> for this task. One more thing, It may be a good idea to try to see if one can make use of the new ISuppostTasks idea whithin <transform>/<apply>. That would mean that people could write simple tasks that just perform an operation on a file by file basis and use <apply> to performe the task on multiple files.
That would mean that the only reason to have the more complicated tasks that do their own dependency checking is for tasks like <javac> with jikes that really can perform much better if all arguments are passed at once. Now, if we could just put all that within a <taskdef> declaration and give new fancy names to the composed tasks. Now that is almost Nirvana. :-) Jose Alberto > -----Original Message----- > From: Jon Stevens [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 23, 2000 1:54 PM > To: [EMAIL PROTECTED] > Subject: Re: New task <transform> committed > > > on 11/23/2000 7:42 AM, "Stefan Bodewig" <[EMAIL PROTECTED]> wrote: > > > <transform> is similar to <execon> in a way. It invokes a given > > command on a couple of files. This task should be used for > executables > > that produce yet another file (_transform_-ing the source > file) as it > > will only invoke the command for source files that are newer than > > their corresponding target files. > > I'm not sure I like <transform> as a name cause other tasks > like <style> are > doing essentially the same thing that you are suggesting the name > <transform> is for. > > Why not: > > <execon transform="true"> > > ? > > -jon > > -- > twice of not very much is still a lot more than not very much >
