Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org Received: (qmail 71274 invoked from network); 1 Mar 2004 23:24:14 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 1 Mar 2004 23:24:14 -0000 Received: (qmail 82271 invoked by uid 500); 1 Mar 2004 23:23:43 -0000 Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 82200 invoked by uid 500); 1 Mar 2004 23:23:43 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 82147 invoked from network); 1 Mar 2004 23:23:42 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 1 Mar 2004 23:23:42 -0000 Received: (qmail 15711 invoked by uid 50); 1 Mar 2004 23:24:15 -0000 Date: 1 Mar 2004 23:24:15 -0000 Message-ID: <20040301232415.15710.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 25373] - Timestamp on generated .java and .class should match the one on .jsp X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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 ------- Additional Comments From kin-man.chung@sun.com 2004-03-01 23:24 ------- I agree this should be a WONTFIX. The time stamps for the .class files indicate the time when they are generated, as they should be. Re-stamping them with different values would have performance impact, without any real benefit. One solution to the "problem" decsribed in your scenario is to touch revision 7 of index.jsp when it is deployed for production, if it is different from revision 6. The automatic recompilation for outdated JSP pages is intended for development, you should precompile your pages when you deploy your application, as Tim suggested. --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org