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 17819 - Allow modules to supply category/"kit" infor:mation; Allow user to download group of modules by selecting a single item in Update Center UI
Summary: Allow modules to supply category/"kit" infor:mation; Allow user to download ...
Status: RESOLVED DUPLICATE of bug 49618
Alias: None
Product: platform
Classification: Unclassified
Component: Plugin Manager (show other bugs)
Version: 3.x
Hardware: PC All
: P3 blocker with 1 vote (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-19 10:04 UTC by _ tboudreau
Modified: 2007-05-21 09:12 UTC (History)
4 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description _ tboudreau 2001-11-19 10:04:29 UTC 
We're seeing a bunch of cases where sets of
related modules need to be downloaded, and it
is difficult to tell what is what.  I think we
need an abstraction ("kit" or "pack") for a
set of modules that are related.  For example,
XML is now divided into I think 6 modules, and
unless someone is developing a module that only
needs to use one of them, a normal user will
probably want all of them.  There should be some
abstraction for groups of modules that makes this
easy for the user.

What I'd suggest is a way of grouping sets of
related modules, so that one can select a 
group (I think "kit" is a good term) of modules
and add that;  if someone wants to drill down
into the individual list of modules, they can.

The downside is that having groups would involve
a change in the data that an update server sends;
the upside is that it should be able to be done
easily in a backward compatible way:  If there
is no category information, the current behavior
would be used.
Comment 1 akemr 2001-11-20 09:12:13 UTC 
It can be easily solved by current Update Center - 
using module groups on server side.
(we are using only Experimental and Extensions now)

These groups can be multilevel, and it's now possible
to add (select to download) whole module group.

You can have e.g. group Extensions -> XML and there have these
6 modules ...

So I suggest to close this ENHANCEMENT and only ask update server
owner (Robert Novak) to create relevant module groups.
Comment 2 Jan Chalupa 2001-11-27 10:51:40 UTC 
Target milestone -> 3.3.1.
Comment 3 Marek Grummich 2002-07-22 08:25:21 UTC 
Target milestone was changed from '3.4' to TBD.
Comment 4 Marian Mirilovic 2003-12-01 10:48:50 UTC 
reassigne to Jirka - new owner of autoupdate
Comment 5 Jiri Rechtacek 2005-04-26 14:27:54 UTC 
It's tracked in issue 49618, this use case has been considered in new Autoupdate
UI (issue 58330).

*** This issue has been marked as a duplicate of 49618 ***