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=25373>. 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=25373 Timestamp on generated .java and .class should match the one on .jsp Summary: Timestamp on generated .java and .class should match the one on .jsp Product: Tomcat 4 Version: 4.0.4 Final Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The timestamp on generated .java and .class files is the time when they are generated and this can cause problems. The timestamp on these files should be exactly the same timestamp as the one on the corresponding .jsp file. Here is an example: - revision 6 of a file called index.jsp is timestamped at May 10, 10:00 am - this revision 6 is labeled and branched for a production rollout - the main branch gets a new revision, not meant for rollout yet: revision 7 at May 11, 9:00 am - the production is finally rolled out on May 12 and the page gets compiled upon the first hit at May 12, 3:00 pm - the index.java and index.class files are stamped with May 12, 3:00 pm - in a month a new production rollout, now revision 7 of index.jsp makes it to the production server - the timestamps are as follows at this point (on the production server): - index.jsp: May 11, 9:00 am (revision 7) - index.java and index.class: May 12, 3:00 pm (based on revision 6) - hits on index.jsp will not trigger a recompile even though they should --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
