DO NOT REPLY [Bug 19293] - jar task does not remove obsolete entries

2003-04-25 Thread bugzilla
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=19293.
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=19293

jar task does not remove obsolete entries





--- Additional Comments From [EMAIL PROTECTED]  2003-04-25 06:43 ---
If you want to remove the files that are no longer present, simply set update to
false.


DO NOT REPLY [Bug 19293] - jar task does not remove obsolete entries

2003-04-24 Thread bugzilla
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=19293.
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=19293

jar task does not remove obsolete entries





--- Additional Comments From [EMAIL PROTECTED]  2003-04-24 21:31 ---
I see that as completely normal... Your are not syncing the JAR with what's in 
your directory, you are updating the JAR, i.e. entries (as picked up by the 
fileset) not already in your JAR are added, and the ones in both that are newer 
are updated. The third kind of entries is left as is, by design.

If you really want to sync, recreate the JAR from scratch. --DD


DO NOT REPLY [Bug 19293] - jar task does not remove obsolete entries

2003-04-24 Thread bugzilla
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=19293.
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=19293

jar task does not remove obsolete entries

[EMAIL PROTECTED] changed:

   What|Removed |Added

   Severity|Normal  |Enhancement



--- Additional Comments From [EMAIL PROTECTED]  2003-04-24 21:46 ---
Couldn't the jar task be made to scan jar files after adding missing or updated 
files, and remove entries that no longer exist in the file system? I realize 
this could be tricky if the jar file is assembled from several sources, and of 
course there is no point in doing so if this procedure would be slower than 
simply recreating the jar file from scratch, as you suggest.


DO NOT REPLY [Bug 19293] - jar task does not remove obsolete entries

2003-04-24 Thread bugzilla
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=19293.
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=19293

jar task does not remove obsolete entries

[EMAIL PROTECTED] changed:

   What|Removed |Added

   Severity|Enhancement |Normal
 Status|NEW |RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2003-04-24 21:55 ---
Actually, there's no such thing as a real JAR update. Ant is forced to fully 
recreate a new JAR under the scene.

As far as doing a real sync, it's technically possible, but would be changing 
the semantic of the JAR task, and breaking backward compatibility, so will not 
be done. Regards, --DD