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 Dev (Build 20111023-372c26dbe8af) VM: Java HotSpot(TM) Client VM, 19.0-b09, Java(TM) SE Runtime Environment, 1.6.0_23-b05 OS: Windows XP User Comments: psomol: After total clean (deletion of all userdirs including testuserdir etc.) I compiled NB from trunk with cluster.config=basic. Then I run the compiled NB, and quite quickly created in it a new JavaFX project. Apparently the NB IDE start-up had not finished yet at the time of new project creation. The new project seems to be created correctly. The exception appeared roughly at the moment when the project creation finished. Stacktrace: java.lang.ClassNotFoundException: org.netbeans.modules.java.hints.bugs.UnusedAssignmentOrBranch$JavaFactoryImpl at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(AccessController.java:0) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Created attachment 112341 [details] stacktrace
Log says Bad file: MultiFileObject@1cea01d7[Editors/text/x-java/org-netbeans-modules-java-hints-bugs-UnusedAssignmentOrBranch$HighlightsFactoryImpl.instance]
Well, both of these registrations have been generated using annotations on the respective classes. So I do not see a bug in java.hints (the client code) that would cause the registration to exist and the class not. So definitely seems like some mistake in the plaform, either in the annotation registration code, or in the classloading/class caching. (Supported by the small amount of reports: if java.hints would really do something wrong that would cause this problems, the exceptions would most likely be thrown for everybody all the time.) Anyway, neither of these classes and their registrations exist after bug #202013.
Thanks for evaluation. If this is inconsistency between layer cache and list of modules, it is covered by issue 195388 *** This bug has been marked as a duplicate of bug 195388 ***