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.
It seems that if you have a lot of autoload modules needed by some real modules, then some eager modules based on the autoload modules, then you turn off the real modules, the eager modules (and autoloads they need) stay on. Observed while trying to implement clusters. Needs investigation and unit tests.
Indeed, trivially reproducible: A autoload, B normal, C eager, B and C both depend on A, all initially enabled, disable B, A and C should both be disabled but are not.
As designed. Eager modules are on whenever they can be on, and will turn on any autoloads they need in the process. If they have *no* regular module dependencies, then for consistency they should always be on. The current behavior is correct. Will add a test to ModuleManagerTest confirming it. In the case of clusters, the simple solution was to make all eager modules autoloads, and require them by the cluster modules.
Resolved for 3.4.x or earlier, no new info since then -> verified.
Resolved for 3.4.x or earlier, no new info since then -> closing.