This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[ JDK VERSION : 1.6 ] Opened a java file in the editor. When to our external SCM application and checked out the file. The editor did not pick up the changed status and left the file as read only in the editor. had to close the file and repoen it before I could edit it.
Reassigning to openide/editor for evaluation.
Filesystems aparently don't fire an event if the file gets older than it was when last checked (e.g. update to clean copy from VCS).
Filesystem impl. really relly on the fact that modified files are newer. If timestamp is changed backward this change isn't captured which is source of reported problem. There is easy fix for this problem but this fix unavoidably means that perf. regression will be caused because instance of FileObject caches System.currentTimeMillis() when initialized. This sort of initialization must have been changed to directly touch a disk and call lastModified. I would like to ask Performance guys if this change is acceptable. If not then this issue will be closed as WONTFIX. Radim, please evaluate and close or reassign back.
Too late for NB5.0, please reevaluate.
*** Issue 58037 has been marked as a duplicate of this issue. ***
To jonhbreen: what is your SCM? Can we find more details how it works? To Radek: can we check the timestamp for a different value rather than newer time?
It is possible that we will change this in the future. Perhaps with a special flag to turn more agressive timestamp checks and keep current bahavior as a default. Closing now as wontfix.
This issue had *1 votes* before move to platform component