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.
Product Version: NetBeans IDE Dev (Build 200902120201) Java: 1.6.0_12; Java HotSpot(TM) 64-Bit Server VM 11.2-b01 System: Linux version 2.6.27-11-generic running on amd64; UTF-8; en_US (nb) Steps to reproduce: - run IDE - open Tools | Plugins - select Java Profiler & push Deactivate button - agree with restart - after restart check status in Plugins dialog again - Java Profiler module is still enabled
I`ve tried 7.0M1 and it worked fine. After that I`ve replaced the autoupdate modules (services and ui) in the 200812310201 daily build (that the oldest daily available now) by the ones from 7.0M1. The result is the same as you`ve described. In other words, with no change in AU, the profiler deactivation was broken somewhere between M1 and daily 200812310201. I`ve also noticed that AU correctly sets "enabled" to "false" in <userdir>/config/Modules/org-netbeans-modules- profiler.xml during restart. But it is changed somehow to "true" while the IDE starting and modules loadeding. Reassigning to profiler for the further evaluation.
Setting "enabled" to "false" in <userdir>/org-netbeans-modules-profiler.xml and setting r/o attribute on this file, result in the following exception when running 200812310201. WARNING [org.netbeans.core.startup.ModuleList] msg Caused: org.openide.filesystems.FSException: File C:\Documents and Settings\Lipin\.netbeans\deveee\config\Modules\org- netbeans-modules-profiler.xml cannot be locked because it is read-only. at org.openide.filesystems.FSException.io(FSException.java:117) at org.openide.filesystems.LocalFileSystem.lock(LocalFileSystem.java:462) at org.netbeans.core.startup.layers.LocalFileSystemEx.lock(LocalFileSystemEx.java:157) at org.openide.filesystems.LocalFileSystem$Impl.lock(LocalFileSystem.java:657) at org.openide.filesystems.AbstractFileObject.lock(AbstractFileObject.java:257) at org.openide.filesystems.MultiFileObject$MfLock.<init>(MultiFileObject.java:1585) at org.openide.filesystems.MultiFileObject.lock(MultiFileObject.java:650) at org.openide.filesystems.MultiFileObject$MfLock.<init>(MultiFileObject.java:1585) at org.openide.filesystems.MultiFileObject.lock(MultiFileObject.java:650) at org.netbeans.core.startup.ModuleList$3.run(ModuleList.java:1049) at org.openide.filesystems.EventControl.runAtomicAction(EventControl.java:120) at org.openide.filesystems.FileSystem.runAtomicAction(FileSystem.java:502) at org.netbeans.core.startup.ModuleList.writeOut(ModuleList.java:1094) [catch] at org.netbeans.core.startup.ModuleList.moduleChanged(ModuleList.java:1254) at org.netbeans.core.startup.ModuleList.flushInitial(ModuleList.java:1164) at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:369) at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:276) at org.netbeans.core.startup.Main.getModuleSystem(Main.java:163) at org.netbeans.core.startup.Main.start(Main.java:304) at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:110) at java.lang.Thread.run(Thread.java:619) ALL [null]: File C:\Documents and Settings\Lipin\.netbeans\deveee\config\Modules\org-netbeans-modules-profiler.xml cannot be locked because it is read-only. With 7.0M1 everything works fine...
Created attachment 76933 [details] messages.log
Not sure what would have changed since M1 - set of included modules maybe?
In Build 090308 everything works fine - the java profiler is correctly uninstalled, furthermore, how can this be caused by profiler? ... Setting to WORKSFORME and reassigning to autoupdate.
v/c