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.
I have a complaint about the VCS (actually JavaCVS) FS used under TreeFS. I can imagine the reply - treefs is not in standard distribution, but that does not matter. There is a problem in VCSFS that guys in web module has to workaround in ugly ways. So I believe that it is important for everyone to improve the VCS: 1. the web DelegatingFS will not need the ugly workarounds 2. the treefs starts to work 3. the web guys will be able to delete its DelegatingFS and start to use the shared instance in treefs That is why I report that some actions (version explorer, refresh and maybe more ) does not work correctly when invoked from TreeFS over JavaCVS.
I believe the fix is not hard. It is just necessary to consistently switch from casting to (VCSFileSystem)fileObject.getFileSystem () to fileObject.getAttribute ("VCSProvider") or something like that. This will work correctly thru any number of MFS on top of VCSFS.
I thought, that Milos uses the attribute approach in JavaCVS. In any case, it has to be fixed in vcscore (and possibly vcsgeneric) modules. I would like to make this change after the vcs APIs will be stabilized. There's an associated issue #19086. Perhaps one should be a duplicate.
things that I figured don't work with treefs, are (in build 200202150100): 1. Versioning explorer action doesn't work, it doesn't open th versionign explorer view and doesn't select the right nodes there. 2. the filesystem actions are not visible in the Versioning menu. I couldn't figure out what's wrong and not working with Refresh..
ok, the things I mentioned in the comment are fixed now.. should work for javacvs and vcsgeneric as well..
verified on NetBeans IDE Development Version (Build 200202190100): The functionality over FSview with cvs actions (popup menu, commands, versioning explorer...) behaves as expected.
Yes, seems to work, except the versioning explorer of course...
what's not working with the versioning explorer?
Resolved for 3.4.x or earlier, no new info since then -> closing.