On Wed, Jun 8, 2011 at 2:34 PM, Justin Deoliveira wrote:
> I think it makes sense... i can't really think of a case where it falls down
> with != .
>
> Andrea, what do you think?
Sounds good to me, Christian go ahead and thanks for the fix! :)
Cheers
Andrea
--
I believe you two are in violent agreement :)
--
David Winslow
OpenGeo - http://opengeo.org/
On Wed, Jun 8, 2011 at 9:08 AM, wrote:
> Zitat von Justin Deoliveira :
>
> > I think it makes sense... i can't really think of a case where it falls
> down
> > with != .
>
> I think almost every backup/
Zitat von Justin Deoliveira :
> I think it makes sense... i can't really think of a case where it falls down
> with != .
I think almost every backup/restore utility would set the original
last access timestamp on restore,
A concrete sample. I use the tar utility to backup user.properties.
Nex
I think it makes sense... i can't really think of a case where it falls down
with != .
Andrea, what do you think?
On Wed, Jun 8, 2011 at 12:36 AM, wrote:
>
> I think that org.geoserver.platform.FileWatcher will not work for
> restored files.
> Method isModified compares with file.lastModified >
I think that org.geoserver.platform.FileWatcher will not work for
restored files.
Method isModified compares with file.lastModified > lastModified
/**
* Determines if the underlying file has been modified since the
last check.
*/
public boolean isModified() {
lo
