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.
in 7.1 beta it is impossible to deactivate Java profiler, it remains active after IDE restart. Possibly related: @see bug http://netbeans.org/bugzilla/show_bug.cgi?id=196406 in which the bugzilla plugin cannot be deactivated.
This is caused by the java.kit module recommending profiler.kit and effectively re-enabling it.
The profiler cluster is non-standard. It is seen as a part of a Java feature, yet it is separated. During work on 7.1 (when profiler between NetBeans, VisualVM and other IDEs) has been standardized, we discussed the possibility to split the profiler implementation between profiler and java clusters. The profiler cluster would contains only generic profiling modules, not depending on java at all. It would depend on platform cluster (possibly, but not necessarily on ide cluster). All the specific integration points would be moved to appropriate clusters (definitely java, possibly enterprise). If this was done, there would be no need for java.kit to recommend profiler.kit.
Will need to be addressed by creating a common Profiler API and moving the implementation modules to appropriate clusters. Not for 7.2
Not for 7.2! I can't believe this.
Well, you better should. The change is not a trivial one and the outcome has very limited value. Currently, everything works as designed/expected - the java cluster recommends turning on the profiler cluster if that is present. If you really want to get rid off the profiler try to uninstall it completely. If the inability to turn off the profiler cluster breaks your IDE completely in a way you can not use it feel free to escalate this issue to P1 (with providing an example how it breaks IDE) and then it will need to be fixed for NB 7.2.
I can't believe it because it suggests bad decision making at a much deeper and more important level.
changing owner