Am 01.04.2015 um 12:45 schrieb ma...@apache.org:
Author: markt
Date: Wed Apr 1 10:45:04 2015
New Revision: 1670609
URL: http://svn.apache.org/r1670609
Log:
Update changelog
Modified:
tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml
Modified: tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml
URL:
http://svn.apache.org/viewvc/tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml?rev=1670609&r1=1670608&r2=1670609&view=diff
==============================================================================
--- tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml (original)
+++ tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml Wed Apr 1 10:45:04 2015
@@ -68,7 +68,15 @@
automatic deployment process, account for the fact that
<code>File.lastModified()</code> has a resolution of one second to
ensure that if a file has been modified within the last second, the
- latest version of the file is always used. (markt)
+ latest version of the file is always used. Note that a side-effect of
+ this change is that files with modification times in the future are
+ treated as if they are unmodified. (markt)
I'm a bit lazy to research this myself and I hope you know instantly:
If the file system is on NFS and the local server is virtualized, it is
not rare, that FS times might be slightly in the future.
Will "files with modification times in the future are treated as if they
are unmodified" change, once the future turns into the past? More
precisely, if the file is changed, its modification time is in the
future (relative to now on the local system), but some time later the
file which was not changed any more now has a mod time in the past
(since "now" advanced on the local system), will it then be detected as
modified?
+ </fix>
+ <fix>
+ Align redeploy resource modification checking with reload modification
+ checking so that now, in both cases, a change in modification time
+ rather than an increase in modification time is used to determine if
the
+ resource has changed. (markt)
</fix>
</changelog>
</subsection>
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
