ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 17934] New: - Dates too late in jar entries
Date Wed, 12 Mar 2003 21:53:51 GMT
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=17934>.
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=17934

Dates too late in jar entries

           Summary: Dates too late in jar entries
           Product: Ant
           Version: 1.5.2
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: bobbymartin@hotmail.com


In 1.5.2, the times on the JarEntries for jar files built with the Jar task are
rounded up instead of down.  When used with, e.g., Weblogic's jspc, this results
in the jsps in the jar file being later than the date compiled into the jsp java
code, and thus the compiled jsps are ignored.  The end result is that when I
build with ant 1.5.2, precompiled jsps are ignored by Weblogic.

I can see in the code on line 960 of
ant/src/main/org/apache/tools/ant/taskdefs/Zip.java, tag ANT_152_FINAL, that
1999 milliseconds are being added to the modification date.  ANT_151_FINAL
doesn't do this.  It appears to me that this is causing the problem.

Strangely, we put a sleep in before the jspc task in our ant script and it still
doesn't fix the out of date issue that we're having.  The only workaround we
have is to use 1.5.1 for now.

Mime
View raw message