Matt Benson wrote:
--- Peter Reilly <[EMAIL PROTECTED]> wrote:
Ah, I see.
This does look like a bug.
Is it? Or is it just the way update="true" works and therefore a documentation issue? From the manual:
The issue was with update="false", not with update="true".
When update is "false", the user wants the set the zip file to the contents of the zip command. Files in the zip file that are not in the zip tasks fileset are removed from the zip file if any of the files in the zip task's fileset are newer that the zip file or are not present in the zip file but this is not the case if the uptodate test is true.
When update="true", the task behaves correctly.
Peter
The update parameter controls what happens if the ZIP file already exists. When set to yes, the ZIP file is updated with the files specified. (New files are added; old files are replaced with the new versions.) ...
Nothing is said about what is done with files currently existing in the archive, but not matched by the zip task. Maybe we only need to clarify this point.
-Matt
__________________________________ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
