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: 1. Start with a clean-built NB source tree. 2. Run ant -f apisupport/build.xml ant -f apisupport/lite/build.xml ant -f utilities/group/build.xml ant -f sysprops/build.xml 3. Run ant -f nbbuild/build.xml tryme 4. Make sure Favorites and Runtime tabs are both displayed. 5. Add to Favorites tab: nbbuild/netbeans 6. Browse to extra/config/Modules dir. You should see four XML files incl. org-netbeans-modules-sysprops.xml. 7. The Runtime tab should be showing System Properties and also Bean Browser. 8. Expand Bean Browser -> Root of system filesystem -> Modules dir. You should see org-netbeans-modules-sysprops.xml among many others. 9. Run: ant -f sysprops/build.xml clean 10. Switch back to the IDE. 11. org-netbeans-modules-sysprops.xml has disappeared from Favorites as expected. 12. BUT it has not disappeared from the system filesystem as shown in Runtime. No change in the Runtime tab observed. (Expected: org-netbeans-modules-sysprops.xml disappears from SFS in Runtime; status bar shows System Properties module being disabled; System Properties node disappears from Runtime tab.) 13. Right-click Modules in SFS in Runtime and choose Refresh Folder. Now the expected changes occur.
Yes, there is invoked refresh on MasterFS after invoking ant script(BridgeImpl) but there is no refresh on SFS. As soon as you invoke it explicitly then everything is OK. Either SFS can listen on MasterFS, filter events and refresh itself eventually or BridgeImpl and other pieces of code must call refresh not only on MasterFS but also on SFS.
Should probably be handled by a general refresh API. I thought there was an RFE filed for a single method call that Ant and other modules could call to trigger a general system refresh, but now I cannot find it.
Reassigning to new module owner jskrivanek.
Is this issue still valid? The original use case is obsolete now.
I don't believe the use case is obsolete. Nothing significant has changed since this was filed AFAIK. It is not a major use case, of course, but there are various miscellaneous situations encountered in module development where you would run into this bug. I could rephrase the request as follows: FileUtil.refreshAll() ought to refresh the SFS in case there have been changes on disk in the $userdir/config/ layer.
Fixed. SFS refresh in FileUtil.refreshAll(). http://hg.netbeans.org/core-main/rev/5f5a2aa54dd5
I think I recall that Wade was actually encountering this recently, trying to set keymaps in the userdir and expecting them to be honored immediately in the running app.
Integrated into 'main-golden', will be available in build *200811200201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/5f5a2aa54dd5 User: Jiri Skrivanek <jskrivanek@netbeans.org> Log: #58663 - refresh default filesystem to reflect possible changes on disk in the $userdir/config.