Bug 228415 - Modules status must be tristate aware
Modules status must be tristate aware
Status: NEW
Product: platform
Classification: Unclassified
Component: Module System
7.4
All All
: P4 (vote)
: TBD
Assigned To: Jaroslav Tulach
issues@platform
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-09 18:27 UTC by ecerichter
Modified: 2013-04-15 17:28 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ecerichter 2013-04-09 18:27:45 UTC
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.

Thanks,

Edson
Comment 1 Jaroslav Tulach 2013-04-09 18:34:22 UTC
As a workaround, uninstall the module, that you don't use. You'll be able to download it when you change your mind.
Comment 2 ecerichter 2013-04-15 17:28:29 UTC
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).

Regards,

Edson


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo