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.
Steps to reproduce: - start NB with one (PHP) project which uses subversion for versioning - switch to console, do a clean clone of the same repository as for project opened in the previous step - change a file in this fresh clone and commit - switch to NB and do svn update via context menu -> result: no FS event is fired but should be for the file changed a while ago in console This problem could be in other versioning modules like CVS, Mercurial etc. as well, not tested. Product Version: NetBeans IDE Dev (Build 090914) Java: 1.6.0_16; Java HotSpot(TM) 64-Bit Server VM 14.2-b01 System: Linux version 2.6.28-15-generic running on amd64; UTF-8; cs_CZ (nb)
we should ensure that after every vcs cmd changing files there will be a fs.refresh however, all fileobject relevant to a php project should be known by filesystem - 170862 would be a way
The fix for post 6.8 should be: FileObject root = findRootOfVCSOperation(); FileChangeListener tmpListener = new MyListener(); root.addRecursiveListener(tmpListener); // do the external command FileUtil.refreshFor(FileUtil.toFile(root)); root.removeRecursiveListener(tmpListener);
PHP attaches its own recursive listener, right? No need to add/remove it before/after every svn action.
So you do > FileUtil.refreshFor(FileUtil.toFile(root)); right?
> So you do > > FileUtil.refreshFor(FileUtil.toFile(root)); > right? As far as i know, we do. We either call it directly here: http://hg.netbeans.org/core-main/file/a19eada68d05/versioning.util/src/org/netbeans/modules/versioning/util/IndexingBridge.java#l160 or through Parsing API if available (the second if branch in IndexingBridge). And since the native listener was introduced, that shouldn't be even necessary, i think.
OK, thanks, I will have a look at it.