ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <bode...@bost.de>
Subject Re: [PATCH] Consolidated copy, move, and delete tasks
Date Wed, 13 Sep 2000 15:58:45 GMT
>>>>> "gm" == glennm  <glennm@ca.ibm.com> writes:

 gm> The biggest difference between these tasks and the current
 gm> delete, deltree, copyfile, and copydir tasks is that the fileset
 gm> is _not_ implicit.  The drawback to this is that it breakes
 gm> existing delete functionality.  The advantage is clarity and
 gm> consistency in the use of filesets.

Any chance to temporarily keep the old behavior within <delete>
(i.e. add an implicit fileset to <delete> and only to <delete>)?

I have no problem removing deprecated things - nothing that has been
deprecated in Ant 1.1 is still present. But if possible we should keep
build files, that were perfectly well adapted to Ant 1.1, working.

I'd propose to add an implicit fileset to delete, emit deprecation
warnings if it is used and remove it right after the next release.

 gm> I'm affraid I deleted the email where Conor explained how to
 gm> include new files in a patch,

Trick CVS into thinking the file has been added (i.e. add an entry for
each file to the corresponding CVS/Entries file).

 gm> Copy

Let's keep the flatten attribute. At least one guy out there seems to
need it 8^).

 gm> Move [...]

 gm> Note that the above move will actually remove the "directory"
 gm> subdirectory of "original".

Is it consistent for <move> to remove (empty) directories but <delete>
to keep them?

Stefan 

- who hasn't found time to actually read your code yet.

Mime
View raw message