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 39182 - org.netbeans.modules.updatecenters should not be eager
Summary: org.netbeans.modules.updatecenters should not be eager
Status: VERIFIED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Autoupdate (show other bugs)
Version: 3.x
Hardware: All All
: P4 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords: ARCH
Depends on: 38143
Blocks:
  Show dependency tree
 
Reported: 2004-01-23 16:31 UTC by Jesse Glick
Modified: 2004-03-18 13:22 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2004-01-23 16:31:42 UTC
I can't see any reason why this module should be
marked eager (modules/eager/*.jar). Please make it
a regular module (modules/*.jar) so it can be
turned off if so desired.
Comment 1 Jiri Rechtacek 2004-01-26 15:34:19 UTC
Jesse. this change was approved by DevRev team (tracked as task 38143)
please open this question/task in issue 38143 to get a conformance. I
close as wontfix for now. Thanks
Comment 2 Jesse Glick 2004-02-16 23:07:21 UTC
You do mention this in issue #38143 and no one objected at the time
but I think it is wrong anyway (I did not have time to look at it
then; and no one explicitly supported the decision there either).

Generally eager modules should only supply internal bridges between
the functionalities of feature modules. This module installs a set of
services which are not necessarily wanted, and as such it should be
possible to turn it off (at least according to current conventions -
might change for D).

Yarda and/or Petr, opinions?
Comment 3 Jaroslav Tulach 2004-02-17 08:39:39 UTC
I've suggested to make it eager under the impression that as soon as
somebody enables AutoUpdate in NetBeans he wants the update centers.
The current behaviour exactly mirrors the one in 3.5 and we wanted to
keep it.

If you see some unwanted functionality you can:
1. disable autoupdate module
2. delete unnecessary update centers
3. do not have the updatecenters module installed at all

The problem with regular module would be that if somebody disables
autoupdate and reenables it, the updatecenters would be gone. 

Jirka's original suggestion was to make autoupdate autoload and the
updatecenters regular module, which seemed to me odd as the autoupdate
contains UI. But still this seems better than two regular modules. So
my own preference is:
1. eager updatecenters
2. autoload autoupdate
3. two regular modules
But as this is really matter of appropriate behaviour everything
depends on what the behaviour should be. 
Comment 4 Jesse Glick 2004-02-17 14:48:38 UTC
"The problem with regular module would be that if somebody disables
autoupdate and reenables it, the updatecenters would be gone." - this
is true of *any* pair of modules with a dependency.

Since you do have a preference and I don't care much about this, will
close again. It is true you can delete the UC services. Nonetheless I
would still recommend two normal modules in this case.
Comment 5 Lukas Hasik 2004-03-18 13:22:28 UTC
x