Every module in NetBeans should be sensitive to three states:
- Auto: module would be activated on demand.
- Active: module should be always available.
- Deactivated: module has been deactivated by user, and should not be loaded automatically - instead, developer should be asked informing why NetBeans believes that it should load this module.
This affects performance and behavior:
1) This conclusion came after long work in issue 228102, where I was suffering poor performance caused by JSF module I do not use (and I don't wish to use anyway in near future). After deactivating the modules, next time I've open the web project, the module has been activated again.
2) As developer, I'm in charge of choosing or not what I want in my cockpit.
3) Activation on demand is of my highest interest, but it should behave in a predictable way.
As a workaround, uninstall the module, that you don't use. You'll be able to download it when you change your mind.
Lowering priority from "absolutely needed" to "nice to have" since there is a completely acceptable workaround.
Thanks for thinking out-of-the-box (which I did not).
I don't have any immediate plans to fix it. Marking won'tfix. I hope the uninstall option is sufficiently playing the "3rd-state". At least it does for me.