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 139792 - Improve module selection for module suite
Summary: Improve module selection for module suite
Status: RESOLVED DUPLICATE of bug 70724
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@platform
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-12 18:43 UTC by maxnitribitt
Modified: 2008-08-18 17:01 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description maxnitribitt 2008-07-12 18:43:01 UTC
It should be easier to include a single existing Module from a cluster to a suite. Right now you can only include all
and exclude the ones you don't need. 

Observed behaviour:

When you have a module suite and you would like to include a single module from a cluster not used before, you need to
select the cluster first to "activate" it. By this you activate all modules in this cluster. Then you have to deselect
all modules except for the one you want. 

Expected behaviour:

It should also be possible to select a single module by checking the check box, even when the cluster is not yet
included. This should in turn activate the cluster, but no additional modules. 

Background:

Clusters are added to the platform.properties files via inclusion by adding them to "enabled.clusters=". Modules on the
other hand are added via exclusion, by unchecking the ones you don't need. I assume the sometimes annoying GUI behaviour
is a result of this design. 


Proposed solution:
To get the expected behaviour it would suffice to add the cluster and exclude all the modules except the one selected.
Comment 1 Tomas Danek 2008-08-18 17:00:33 UTC
i think it is a duplicate of http://www.netbeans.org/issues/show_bug.cgi?id=70724, which is fixed by now. Could you
please reopen if you do not think so?

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