Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Message-ID: 
 <E1B81A5627BAD01191B500805FC16B0E77AB76@nlnwx001.nwgbak.nl.origin-it.com>
From: "Kuiper, Arnout" <Arnout.Kuiper@nl.origin-it.com>
To: "'ant-dev@jakarta.apache.org'" <ant-dev@jakarta.apache.org>
Subject: RE: Task functionality next version Ant
Date: Sun, 14 May 2000 14:36:55 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"

Oops, trigger fingers.

> > -----Original Message-----
> > From: Stefan Bodewig [mailto:bodewig@bost.de]
> >  KA> Now we are talking about task functionality here, how about
> >  KA> defining some for the next version Ant.
> > 
> > I agree with all of what you've written and just want to 
> add that move
> > would probably need a "forceoverwrite" attribute, too.

Agreed.

> > The optional RenameExtensions tasks lokks a little bit as if it
> > belonged into the move category. I'm not sure.

Could be, but it is a bit tricky.
What "RenameExtensions" does, fits in the category of renaming
a file with "Move". If we want to include the "RenameExtensions"
functionality in "Move", than I propose to make it more general,
and allow to change filenames (pathnames?) with the use of some
regexp. Such that you can rename for instance all ".java" files
to ".java.orig".

This is a nice add-on, but I think we should stick to the simple
"Move" version first, before adding the more complex regexp stuff.

> > IIRC Thomas Haas has written a task that consolidates text
> > manipulation taks (FixCRLF, KeySubst, Replace).

Agreed.

> > Expand and Zip could be put together into a single task.

Personally I would keep these separated (and rename expand to
unzip). The same holds for jar and unjar and gzip and gunzip.


  -Arnout