You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2001/12/06 09:47:47 UTC
DO NOT REPLY [Bug 5092] -
task always rebuilds
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=5092>.
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=5092
<jar> task always rebuilds
------- Additional Comments From tom_brus@nl.compuware.com 2001-12-06 00:47 -------
This bug bit me to. I have a simple fix for this bug that, as far as I can see,
is a permanent fix. This is a bug in class Zip, not Jar, so it has more impact
then just Jar.
Analysis:
When isUpToDate() is called the zipFile does not exist anymore because class
Zip has renamed it to tmp.<i> in execute() just before calling isUpToDate().
Therefore Jar can not open the file and considers it out of date.
I believe that Zip's isUpToDate() also checks if the file exists and will
therefore also always consider it out of date.
Fix:
Swap the rename and uptodate check code in execute() in Zip.
I will attach a patch.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>