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.

Bug 22536

Summary:	Eager and autoload modules do not work perfectly together
Product:	platform	Reporter:	Jesse Glick <jglick>
Component:	Module System	Assignee:	Jesse Glick <jglick>
Status:	CLOSED INVALID
Severity:	blocker
Priority:	P2
Version:	3.x
Hardware:	PC
OS:	Linux
Issue Type:	DEFECT	Exception Reporter:

Description Jesse Glick 2002-04-17 14:07:50 UTC

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.

Comment 1 Jesse Glick 2002-05-08 22:18:23 UTC

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.

Comment 2 Jesse Glick 2002-05-10 16:24:16 UTC

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.

Comment 3 Quality Engineering 2003-07-01 16:01:17 UTC

Resolved for 3.4.x or earlier, no new info since then -> verified.

Comment 4 Quality Engineering 2003-07-01 16:28:14 UTC

Resolved for 3.4.x or earlier, no new info since then -> closing.