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 61757 - Project Wizard Locked - "Project folder is read only"
Summary: Project Wizard Locked - "Project folder is read only"
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: issues@javaee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-03 13:46 UTC by lucasfigueiredo
Modified: 2005-08-11 11:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lucasfigueiredo 2005-08-03 13:46:21 UTC
"New Project", "Web Application with existing sources" or "Web Application"
Wizard does not work properly under my WinXP environment. The dialog informs
that "project folder is read only" for several folders I select. Hence, the
"next" button remains locked and I cannot create my project!

Aparently the IDE reconizes some folders as if they are system folders or locked
by OS. 

Other related issue I found : 60774

Thanks,
Lucas
Comment 1 zikmund 2005-08-08 10:06:42 UTC
Does the same thing happen for Java Project in the same directory?
Could you please try it in root directory (e.g. C:\TestProjects). If it fails,
please investigate which directory access right is reason of your failure. Thanks!
Comment 2 lucasfigueiredo 2005-08-10 21:00:24 UTC
Thanks,

It seems that the WinXP locks some directories without asking anything. A "green
square" (not a normal check mark) appears in the "read-only" property of the
directory and, no matter how many times you uncheck this property, the IDE still
recognizes the directory as read-only. 

To solve this trouble, I had to a) rename the old directory, b) create a new
directory with the old name and then the wizard worked.

Comment 3 zikmund 2005-08-11 11:40:34 UTC
OK, then marking as WontFix since it is problem of Java/WinXP. Thanks for
investigation.