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.
Build: NetBeans IDE 6.1 (Build 200804211638) VM: OpenJDK Client VM, 1.6.0-b09, OpenJDK Runtime Environment, 1.6.0-b09 OS: Linux, 2.6.24-17-generic, i386 User Comments: Created a new Desktop Application but it will not open in the editor.
Created attachment 62205 [details] stacktrace
After this error, I could not open or create any new projects. I decided to reinstall NetBeans and wipe the .netbeans user directory. It now works fine.
Seems to be serious, if project cannot be created -> P2
Seems that passed evaluator is null, or the evaluator.getProperties() returned null - this may happen if the mapping could not be computed (e.g. due to a circular definition).
Created attachment 62911 [details] stacktrace
Created attachment 62912 [details] stacktrace
*** Issue 137409 has been marked as a duplicate of this issue. ***
Changed to better exception. 7da8fc525909 I've did evaluation and found that the evaluator cannot be null, so the evaluator.getProperties() returned null. This can happen when the project is so broken that the properties cannot be determined. If you have such a broken project, please attach the ${nbuserdir}/build.properties file. Thanks
Created attachment 63186 [details] stacktrace
Created attachment 63287 [details] stacktrace
Created attachment 63302 [details] stacktrace
Please, can someone attach the project causing the NPE?
Created attachment 63458 [details] stacktrace
Created attachment 63596 [details] stacktrace
Created attachment 63795 [details] stacktrace
Build: NetBeans IDE Dev (Build 200806240008) VM: Java HotSpot(TM) Client VM, 1.5.0_15-b04, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_15-b04 OS: Windows XP, 5.1, x86 User Comments: Trying to open a Java Class Library project which I had renamed using the "rename" menu item on the project node.
Created attachment 64248 [details] stacktrace
*** Bug 197841 has been marked as a duplicate of this bug. ***