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.
It is not possible to create new empty javafx project. Every time the 'Finish' button in the new project dialog is pressed, a warning 'Project folder already exists and is not empty' is shown and the project is not created and opened. Product Version: NetBeans IDE Dev (Build 201307212300) Java: 1.7.0_40-ea; Java HotSpot(TM) 64-Bit Server VM 24.0-b53 Runtime: Java(TM) SE Runtime Environment 1.7.0_40-ea-b34 System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb) User directory: C:\Users\jprox\AppData\Roaming\NetBeans\dev Cache directory: C:\Users\jprox\AppData\Local\NetBeans\Cache\dev
It happens for javase project as well. It happen only on jdk1.7.0_40, on jdk1.7.0_25 it works well
Similar problem with JavaEE projects. There seems to be problem only with 7u40 build 34. Build 33 works fine.
(In reply to comment #2) > Similar problem with JavaEE projects. There seems to be problem only with 7u40 > build 34. Build 33 works fine. This is the changelog of b34: http://download.java.net/jdk7u40/changes/jdk7u40-b34.html
*** Bug 233127 has been marked as a duplicate of this bug. ***
Anything suspicious in the messages.log? Can anyone with the affected build installed attach it? Thanks.
Created attachment 137593 [details] messages.log
The problem is in GeneratedFilesHelper.generateBuildScriptFromStylesheet failing to do XSLT transformation. I am downloading 1.7_40 to find out more.
related/duplicate of issue 233143
The problem is in com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.setProperty (SAXParserImpl.java:545) which does not check the fSAXParser for null, see http://hg.openjdk.java.net/jdk7u/jdk7u40/jaxp/diff/4149e4abea17/src/com/sun/org/apache/xerces/internal/jaxp/SAXParserImpl.java
*** Bug 233143 has been marked as a duplicate of this bug. ***
(In reply to comment #9) > The problem is in > com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.setProperty > (SAXParserImpl.java:545) > which does not check the fSAXParser for null, see > http://hg.openjdk.java.net/jdk7u/jdk7u40/jaxp/diff/4149e4abea17/src/com/sun/org/apache/xerces/internal/jaxp/SAXParserImpl.java Tonda, could we escalate ?
Filed as a P1 for 7u40, #8021148. Closing this issue on NB side.
Sorry, I am new programming. I'm not following the below chain of comments entirely. What can I do so I can create projects with NetBeans and start learning programming?
(In reply to comment #13) > Sorry, I am new programming. I'm not following the below chain of comments > entirely. What can I do so I can create projects with NetBeans and start > learning programming? You will run into this bug only if you start NetBeans with JDK 7u40 b34 (a promoted build of a not yet final 7u40 release). Use your NetBeans installation with the latest released JDK 7u25 and you will not encounter this problem.
*** Bug 233537 has been marked as a duplicate of this bug. ***
Could you please add JDK8 b101 as affected version in the official bugtracker - it just says fixed for u40 b36 - so we should make sure it gets into jdk8 as well. Thanks
(In reply to comment #16) > Could you please add JDK8 b101 as affected version in the official bugtracker - > it just says fixed for u40 b36 - so we should make sure it gets into jdk8 as > well. Thanks This has been taken care of by Java team. The JDK bug lists related issues and one of them is a backport of the fix into 8. http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8021148 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8021428
*** Bug 234036 has been marked as a duplicate of this bug. ***
*** Bug 236560 has been marked as a duplicate of this bug. ***
I'm getting the same issue. I already cleared my user dir and the issue temporarily went away, but is back after about an hour. What was the fix for this?
(In reply to joshualee from comment #20) > I'm getting the same issue. I already cleared my user dir and the issue > temporarily went away, but is back after about an hour. What was the fix for > this? This is a two years old bug on JDK side which was fixed in both 7u40 and 8. Do not reopen. Instead file a new bug with details of your NB version, Java version, OS, and steps to reproduce.