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.

Bug 151392

Summary: The folder RO flag is not handled correctly
Product: platform Reporter: jirka_x1 <jirka_x1>
Component: FilesystemsAssignee: Jiri Skrivanek <jskrivanek>
Status: RESOLVED DUPLICATE    
Severity: blocker CC: mpetras
Priority: P3    
Version: 6.x   
Hardware: PC   
OS: Windows XP   
Issue Type: DEFECT Exception Reporter:
Attachments: Cannot create subdirectory "X" of Documents
New folder icon incorrectly disabled in the Documents folder

Description jirka_x1 2008-10-26 14:18:43 UTC
In various Open/Save dialogs, including the a New Project dialog, the IDE thinks it cannot create subdirectory of the
windows Documents directory (My Documents on XP), claiming the project is read-only (see attachments). 

However, Windows uses the RO flag not to mark the folder as read-only, but as customized
(http://support.microsoft.com/kb/256614). So netbeans should ignore that flag on folders. 

Workaround: Create the directory in any program that knows how directory permissions in  Windows work (e.g, Win
Explorer, Total Commander, etc)

This affect not only Win XP but also Win Vista (I could not select it in the OS list)
Comment 1 jirka_x1 2008-10-26 14:20:38 UTC
Created attachment 72662 [details]
Cannot create subdirectory "X" of Documents
Comment 2 jirka_x1 2008-10-26 14:21:56 UTC
Created attachment 72663 [details]
New folder icon incorrectly disabled in the Documents folder
Comment 3 Jana Maleckova 2008-10-26 22:04:46 UTC
reassign to openide for evaluation
Comment 4 Jiri Skrivanek 2008-10-27 09:55:28 UTC
It is a bug in JDK and it is fixed in JDK7 (see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4939819). As default
target for NetBeans projects is suggested C:\Documents and Settings\me\My Documents\NetBeansProjects.


*** This issue has been marked as a duplicate of 50143 ***
Comment 5 jirka_x1 2008-12-22 16:20:09 UTC
It seems weird to wait for JDK 7 which won't be out for another year, when the work-around for this bug is about 2 or 3
lines of code (check read-only only if not on windows)