Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Date: 4 Sep 2003 10:58:53 -0000
Message-ID: <20030904105853.1474.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: dev@ant.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 22930] New:  -
    New update mode in zip (and related) task

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22930>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22930

New update mode in zip (and related) task

           Summary: New update mode in zip (and related) task
           Product: Ant
           Version: 1.5.4
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: simon.spruzen@rbos.com


I'd like to request a new mode in the zip (and related) tasks. If I have 
update="true" (to bang on an existing zip file), I'd like a way of specifying 
that files listed in the nested zipfileset or fileset elements *must* be added 
to the zip, even if the new file's mod date is before the duplicate file in the 
zip archive.

Perhaps this could be acomplished through a new option for the duplicate 
attribute:

replace - force the replacement of the file present in the zip file with the 
new file, even if the new file is older than the existing file.

This would be different to the 'add' setting (which would lead to two files).


simon.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org