tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 33453] - Jasper should recompile JSP files whose datestamps change in either direction (not just newer)
Date Tue, 08 Feb 2005 23:46:40 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33453>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33453





------- Additional Comments From rainer.jung@kippdata.de  2005-02-09 00:46 -------
Although not allowed to vote I have an opinion: The dynamic update feature for
JSPs comes from the need to dynamically manage content without a heavy weight
administrative action.

But every now and then one has to roll back a change. With static content you
would just put back the original files. It would be very nice, if it would work
the same way with JSPs, especially because that's unsually the unplanned case
(roll back) where you need to have a simple procedure.

I know, you could touch the old file. Myself I always tell Sysadmins to make
backup copies and roll back file changes with "cp -p", so that the files keep
their original timestamp, which is a nice low-level approximation of checksums.
Any higher level tool (like CVS) will most liekely also roll back including file
timestamps.

There seems to be very little risk in the change and some not neglectable benefit.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message