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 bug was originally marked as duplicate of bug 199735, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related. Build: NetBeans IDE 8.0.2 (Build 201411181905) VM: Java HotSpot(TM) 64-Bit Server VM, 25.5-b02, Java(TM) SE Runtime Environment, 1.8.0_05-b13 OS: Windows 7 User Comments: pkevin: Build and deploy web application. Stacktrace: java.io.IOException: C:\Program Files\NetBeans 8.0\unknown at org.openide.filesystems.FileUtil.createFolder(FileUtil.java:472) at org.netbeans.modules.j2ee.deployment.impl.ServerFileDistributor._distributeOnSave(ServerFileDistributor.java:372) at org.netbeans.modules.j2ee.deployment.impl.ServerFileDistributor.distributeOnSave(ServerFileDistributor.java:224) at org.netbeans.modules.j2ee.deployment.impl.TargetServer.distributeChangesOnSave(TargetServer.java:249) at org.netbeans.modules.j2ee.deployment.impl.TargetServer.notifyArtifactsUpdated(TargetServer.java:883) at org.netbeans.modules.j2ee.deployment.impl.DeployOnSaveManager$DeployTask.notifyServer(DeployOnSaveManager.java:548)
Created attachment 151511 [details] stacktrace
Please can you provide more details on this? What server did you used? What is the project layout? Were there any other actions before the deploy? Thanks in advance.
Wish I could tell you more. I'm not sure what server I was installing on because I've been working on moving my web app to Glassfish 4. But, since the application is still in development I may have also been installing on 3.1.2.2. I can tell you that it is a Vaadin 7.3.7 application using maven for build configuration. It is possible that this error resulted from any of a number of scenarios as I believe it was one of my first install attempts on 4.0 and there may have been some missing dependencies for that environment. Also, it's possible that I didn't see the exception right when it happened since the only notification was the little bubble at the bottom of the window. It was also probably early in the set-up process where I was still configuring jdbc pools and connections, and perhaps there was a configuration mismatch in that regard. As I continue to deploy to the 4.0 server, I will try to be more vigilant in case the error repeats itself. Let me know if there is anything else I can help with.