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 163450 - java.io.IOException: Project folder is not writeable.
Summary: java.io.IOException: Project folder is not writeable.
Status: NEW
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: TomasKraus
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-23 09:53 UTC by Marian Mirilovic
Modified: 2013-12-12 10:18 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 145377

Attachments
stacktrace (2.84 KB, text/plain)
2009-04-23 09:54 UTC, Marian Mirilovic 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Mirilovic 2009-04-23 09:53:59 UTC 
Build: NetBeans IDE 6.7 Beta (Build 200904230001)
VM: Java HotSpot(TM) 64-Bit Server VM, 11.3-b02, Java(TM) SE Runtime Environment, 1.6.0_13-b03
OS: Linux, 2.6.27-11-generic, amd64

User Comments:
mmirilovic: tried to reproduce issue 149920



Stacktrace: 
java.io.IOException: Project folder is not writeable.
        at org.netbeans.api.project.ProjectManager.saveProject(ProjectManager.java:654)
        at org.netbeans.modules.j2ee.sun.ide.j2ee.BuildExtension.abbreviateBuildXml(BuildExtension.java:146)
        at org.netbeans.modules.j2ee.sun.ide.j2ee.ModuleConfigurationImpl$StaticBuildExtensionListener.rewriteBuildImpl(ModuleConfigurationImpl.java:356)
        at org.netbeans.modules.j2ee.sun.ide.j2ee.ModuleConfigurationImpl$StaticBuildExtensionListener.access$100(ModuleConfigurationImpl.java:316)
        at org.netbeans.modules.j2ee.sun.ide.j2ee.ModuleConfigurationImpl$StaticBuildExtensionListener$1.run(ModuleConfigurationImpl.java:412)
        at org.openide.util.Mutex.postRequest(Mutex.java:1251)
Comment 1 Marian Mirilovic 2009-04-23 09:54:06 UTC 
Created attachment 80745 [details]
stacktrace
Comment 2 Milos Kleint 2009-04-23 10:40:33 UTC 
see issue 91398 for explanation why the exception is thrown with the current wording.

reassigning to web projects as these shall catch the exception and react to it somehow I guess.
Comment 3 David Konecny 2009-04-23 21:16:32 UTC 
Transplant Milos' fix to all J2EE projects - 26c7930d9c08. I think exception text pretty much says what's wrong -> P4.
Comment 4 Martin Janicek 2013-12-12 10:18:46 UTC 
Nothing to do on Web project side, reassigning to GF. ModuleConfigurationImpl.StaticBuildExtensionListener.rewriteBuildImpl(..), line 364 should do the same as described in comment 3