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.
I just downloaded the recent install of NBeans (200803021202) and after the install, got a WARNING message upon startup that Web Services and CSS Visual Editor modules could not be located.
could you please attach the screenshot of the error and messages log?
Created attachment 57734 [details] Screenshot of Error
Created attachment 57735 [details] Screenshot of Error
I have attached the screenshot, but I cannot locate the messages logs file. Where is it located?
thanks for the screenshot. The messages.log file is located at %USERPROFILE%/.netbeans/dev/var/log/ Thanks, Dmitry
Created attachment 57736 [details] Messages log
I see the problem with CSS: INFO [org.netbeans.core.startup.NbEvents]: Warning: the module C:\java\netbeans-6.1\200803021202\modules\org-netbeans- modules-css2.jar could not be found, ignoring... WARNING [org.netbeans.core.startup.ModuleList]: Error encountered while reading org.netbeans.modules.css2 java.lang.NullPointerException [catch] at org.netbeans.core.startup.ModuleList$1.run(ModuleList.java:248) at org.openide.filesystems.EventControl.runAtomicAction(EventControl.java:120) at org.openide.filesystems.FileSystem.runAtomicAction(FileSystem.java:499) at org.netbeans.core.startup.ModuleList.readInitial(ModuleList.java:166) at org.netbeans.core.startup.ModuleSystem.readList(ModuleSystem.java:262) at org.netbeans.core.startup.Main.getModuleSystem(Main.java:173) at org.netbeans.core.startup.Main.start(Main.java:325) at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:110) at java.lang.Thread.run(Thread.java:619) Seems that the cluster name is missing in css2 path (who knows why...) C:\java\netbeans-6.1\200803021202\modules\org-netbeans-modules-css2.jar
Thanks for looking into this so quickly.
Can you please try with a clean NB settings directory (C:\Documents and Settings\yourname\.netbeans\dev)? There have been changes in the list of modules, so this may be the problem.
I have not had this problem with any of the later releases, only this one.