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.
As there is a long-term goal to abandon VCS FS it would be nice to document and track what is currently blocking this effort. At least two issues were mentioned on the review: FileObject.lock() can result in visual asking whether a readonly file should be checked out and made read-write (e.g. for Visual SourceSafe) VCS FS is sensitive to ongoing update running which could overwrite the files on the disk however if those files would be opened in the editor and possibly modified there would be a potential dataloss. The changes made in the file by the VCS update would be overwritten by the editor when the file would be saved.
Removed TCR keyword. This issue is still importnant though it's not critical for the currently discussed solution.
Tomas could you link the analysis document, please?
There is no such document to link. I created a list of FS roles in VCS as part of one document, but the list is likely incomplete, and the document talks about way too many other things. I expected someone having deeper understanding of VCS would write this list. My observations about VCS FS roles were (excluding roles already replaced): * providing annotations and actions for UI * virtual files (just locally removed) * locking files during update * automatic checkout/edit (when a file is requested to be edited) * intercepting file operations (not sure if currently used) VCS FS is used also for many other things (as it is config root for everything), but those are not related to the FS API.