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.
## Description When a 'PHP Application With External Sources' project's directory is an NFS mount, external changes to the project files (i.e., changes made directly on the system exporting the NFS mount) causes undesirable behavior in NetBeans: - Filesystem changes (moved/renamed files, etc.) will not appear at all in the Projects view. - Files that were modified externally will not open in NetBeans at all; the IDE must be quit and relaunched first. Quitting and relaunching NetBeans IDE will resolve the issue (until external changes are made again). ## Steps to reproduce: - System A is the system on which the NetBeans IDE is running. - System B is another system (e.g., virtual machine) exporting the project files via NFS. 1. Mount the NFS share containing the code files from System B onto System A. - I'm using autofs on Mac to automount the share. I have not tested it with a manual mount. 2. Create a new "PHP Application With Existing Sources" project and set its "Sources Folder" to the mounted NFS share. 3. Make a change to the files on System B. 4. The changes will not be reflected in NetBeans: - Filesystem changes (moved/renamed files, etc.) will not appear at all in the Projects view. - Files that were modified externally will not open in NetBeans at all; the IDE must be quit and relaunched first. ## Additional information: Problem can be reproduced consistently with the following setup: - System A (NetBeans): Mac OS 10.5 (using Apple's autofsd, which might operate differently from *nix's autofs), NetBeans 7.1, PHP plugin 1.22 - System B (NFS Server): CentOS 6, nfs-utils.i686 1:1.2.2-7.el6
Reassigning to the proper component, please evaluate. Thanks.
Since 7.0 NetBeans rely on inotify & similar OS tools to deliver events about changed files. In case you have NFS mount and make changes from "system B", the "system A" does not deliver any changes (probably). There is not much to do about it, except to return back to pre-7.0 behavior: a) Run with -J-Dorg.netbeans.modules.masterfs.watcher.disable=true b) install "Scan On Demand" module and refresh folders manually: http://wiki.netbeans.org/ScanOnDemand Let us know if one of the above works for you.
Installing the Scan on Demand module does work around the issue (although it does introduce an undesirable side effect - NetBeans no longer auto-scans my project, which causes problems when e.g., adding new libraries to the project's Include Path). I will try setting the -J-Dorg.netbeans.modules.masterfs.watcher.disable=true flag in netbeans.conf and see if that has an effect. I apologize for mentioning the E-word, but I have noticed that Eclipse does not have this problem (verified in PyDev project). Perhaps Eclipse simply works similarly to NetBeans's pre-7 behavior, but it does make me curious whether there might be an additional alternative that has not been considered?
Adding `-J-Dorg.netbeans.modules.masterfs.watcher.disable=true` to netbeans.conf does appear to solve the problem without introducing any significant side effects.
Good to know alternatives exists. Re. E!E - I guess they don't scan sources for external changes at all. Probably only detect the change when a file is being open. If you can investigate more about the actual behavior, we may try to mimic it.
On remote disks (NFS, SMB, iPod) the native notification does not work on Mac. But the the core.framework can tell you all the mount points.
Do you think there might be an option or flag I can set, either on the NFS server or in OS X's autofs that might have an effect on this behavior? I'm unfortunately not knowledgeable enough to do all the research on my own, but if you could explain to me what I need to ask for, I am more than happy to do the legwork to post around on e.g., Stackoverflow to gather more information on the different systems involved and what might be going on (or not, as the case may be).
As far as I know (but I am not NFS expert) the inotify (used on linux for native listening) does not support it. The FAM (file access monitor) supported it in some way for NFS.
Are you REALLY sure you don't want to fix this? Other editors don't have that issue, it is easy to fix and the problem is a SHOWSTOPPER at least for all people in my office. Suggested fix: Other editors simply check the "last modified" date of a) either the files that are currently open, OR b) at least the 1 file that currently has the focus in the editor. There is no need to check the whole project (other editors don't do it either), but for the files that are currently open, the effect is quite noticeable (and annoying). The problem is obviously easy to fix for 80% (of all common cases in everyday work) with little overhead. So why don't give it a try.
I have a feeling our editor checks the timestamps. If not, we can fix it. However this is far from the scope of the original bug report. Probably just report new bug for platform/text.
Thank you. As requested I opened a new issue: Bug 206182.