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.
Well, I can't say thet it behaves bad. But from the user point of view who is working with ide, it behevas suspiciously. Problem is that IDE makes unvisible files in each dir of its FileSystems: .nbattrs .nbattrs~ The best it'll be to show you on example: 1.Have one repository and checkout it into 2 workings (2 FSs) 2. Suppose that you have there this dir structure in your repository and workings: test/bla/ ahoj.java 2a If you open and edit file in the ide editor. The VCS FS will create also backup file if ahoj,java 3. in the first working on test dir run cvs->remove command and commit it. 4. in the second working dir perform cvs->update -P on the root of your FS. ------ 5. User might expect that all dir structure starting with "test" should dismiss from the FS, but dir structure will resist here seeming it's empty. ------ Problem is that IDE makes its supported files ".nbattrs" in each dir of mounted FSs. Also problem might be that VCS FS (or all types of FS? or just only editor) creates backup files of edited files. then CVS-UPDATE -P behaves correctly from the point of command line behaviour. But from IDE view which tries to hide some files, that common user doesn't have any ide that there exists such files, it is not correct, I think. I hope it's at least little bit clear what I wished to explain.
Set target milestone to TBD
Moving to CVSlite.
-P could also delete saved revisions such as x.java.~1.2~ or .#x.java.1.2