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.
This is a request to prevent another user from accessing another user's working directory. If 2 users try to access the same working directory then exceptions occurs while executing check-out: Mon Dec 02 14:10:31 PST 2002: java.io.FileNotFoundException: /export/home1/cfqa1/work/PartSupplier2CMR/Data2/CVS/netbeans.cmd.cache (Permission denied) java.io.FileNotFoundException: /export/home1/cfqa1/work/PartSupplier2CMR/Data2/CVS/netbeans.cmd.cache (Permission denied) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.<init>(FileOutputStream.java:176) at java.io.FileOutputStream.<init>(FileOutputStream.java:131) [catch] at org.netbeans.modules.vcscore.caching.VcsCacheDir.writeToDisk(VcsCacheDir.java:338) at org.netbeans.modules.vcscore.cache.CacheDir.setComplete(CacheDir.java:325) at org.netbeans.modules.vcscore.cache.CacheQueue.run(CacheQueue.java:57)
IMHO no such restriction should be made. The users should know what they are doing. But perhaps the cache infrastructure should be more robust to be able to live somehow without access to CVS/netbeans.cmd.cache.
New users to CVS may not know what they are doing or may make a mistake and accidently try to make changes to someone else's working directory.
I do not see why NetBeans should not allow users to make changes in someone else's working directory if the OS permits it. I see this as a problem of the OS or it's setup and NetBeans should not try to solve it, because they can not do it well. How do you suppose, that NetBeans should recognize that one user is going to use a working directory of another user?? There is no user info in java.io.File. And even if it would be possible I'm not convinced, that NetBeans should do it. However the problem is, that when the cache files are not writable a lot of exceptions is thrown (although they probably do not hurt anything). The cache infrastructure should be able to live without being able to store anything to the disk.
OK, there might be a situation where a user needs to use another's working directory. At least if the directory is not writable then the exception should be caught.
Changing to defect. The exception must be processed somehow, the FS must be usable even if the cache information can not be written.
*** Issue 29514 has been marked as a duplicate of this issue. ***
The problem of permissions when writing to VCS cache is a duplicate of the recently reopened issue #16295. The cache functionality must survive permission problems and do not bother the user with every unsuccessfull disk access. *** This issue has been marked as a duplicate of 16295 ***
Agreed. Verified as duplicate of another bug about more robust cache.