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 201011210001) Operating System = Windows XP version 5.1 running on x86 Java; VM; Vendor = 1.6.0_20 Runtime = Java HotSpot(TM) Client VM 16.3-b01 If you disable Base IDE plugins, then restart the IDE and re-enable the Base IDE plugins, the IDE Branding plugin is not re-enabled. Steps to reproduce: 1) Clean UserDir 2) Launch IDE 3) Disable all plugins (including Base IDE) 4) Restart IDE 5) Enable Base IDE plugin
If it does not work, don't do it.
You missed the point. If you disable the module and re-enable it, it should re-enable all parts. Not a subset.
I don't think I missed anything. Just don't disable IDE Base. It makes little sense anyway.
I don't disagree that it doesn't make sense. Unfortunately the fact that it doesn't make sense doesn't mean a user will never do it, whether by accident (as was the case with me) or because they think they can because the IDE doesn't stop them. Either way, this can happen. And when it does, if the user attempts to re-enable the IDE Base modules, not all of them will be re-enabled.
After doing the above following modules remain disabled: $ grep enabled.*false nbbuild/testuserdir/config/Modules/* nbbuild/testuserdir/config/Modules/org-netbeans-modules-autoupdate-pluginimporter.xml: <param name="enabled">false</param> nbbuild/testuserdir/config/Modules/org-netbeans-modules-ide-branding-kit.xml: <param name="enabled">false</param> nbbuild/testuserdir/config/Modules/org-netbeans-modules-uihandler-exceptionreporter.xml: <param name="enabled">false</param> nbbuild/testuserdir/config/Modules/org-netbeans-modules-welcome.xml: <param name="enabled">false</param>
All of these modules come from nb cluster.
Let's give up and live with current behavior.