>>>>> "KA" == Kuiper, Arnout <[EMAIL PROTECTED]> writes:
>> > -----Original Message----- > From: Stefan Bodewig >> > The optional RenameExtensions tasks lokks a little bit as if it >> > belonged into the move category. KA> Could be, but it is a bit tricky. KA> If we want to include the "RenameExtensions" functionality in KA> "Move", than I propose to make it more general, and allow to KA> change filenames (pathnames?) with the use of some regexp. Hope we are not approaching Perl here 8^). Pathnames would really be too much I guess. And once you open up the box with regexps here you will probably need something like "calculated replacements" for the patterns - i.e. something like Perl's s/(\w+)/lc($1)/ge that would then change all filenames to be all lowercase etc. I'm sure something like this would be useful for some people. But you are right, this functionality should be separated into a different task - which doesn't need to be part of the core anyway. >> > Expand and Zip could be put together into a single task. KA> Personally I would keep these separated (and rename expand to KA> unzip). The same holds for jar and unjar and gzip and gunzip. as well as tar and untar. AFAIK zip is currently the only "compression" operation with a task for decompression. I thought after putting together expand and zip into one task we could have a consistent interface for the other tasks, something like a boolean "expand" attribute. If we'll keep expand (I'd prefer the name unzip in this case as well) and zip as different tasks then we should implement all the reverse tasks as tasks of their own as well. Stefan
