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 73555 - Install Modules should have Select All Option.
Summary: Install Modules should have Select All Option.
Status: RESOLVED INVALID
Alias: None
Product: platform
Classification: Unclassified
Component: Autoupdate (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: nbbuild-issues@ide
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-13 19:09 UTC by jlam
Modified: 2006-03-14 09:33 UTC (History)
1 user (show)

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 jlam 2006-03-13 19:09:56 UTC
When updating Netbeans with my own modules, I have to click through and select
each and every module to Install.  This add up when it is on the order of 30. 
Please provide a "Select All" button or have all selected by default.

You see this in the Update Wizard under:
--------------
View Certificates and Install Modules:
Select the modules you wish to install.  If a module is signed you must view and
accept its certificate.
--------------

Thanks,
Joelle
Comment 1 rbalada 2006-03-14 09:33:07 UTC
Joelle,

here's my statement. I can see two potential issues here and I'm unclear which
is the one you want to fix.

1) I'm experienced with a buildsystem running in 'on top of NetBeans IDE binary'
mode. This build mode requires that respective downstream product buildsystem
has to replace IDE's keystore in platform6/core/ide.ks file. This allows that
update client in final product can recognize NBMs signed with either NetBeans or
(in this case) Creator's key. If this is the case, contact your Build
Engineering team and request them to fix it.

2) You're requesting an enhancement for the 'autoupdate' module in release
'5.0'. I can see two good reasons why not go this way. Each reason is IMHO
enough strong to act standalone.
reason1: it explicitly allows uneducated&uninformed acceptance of incorrectly
signed NBMs. This is a risk. If we do that, than we would put down signing of
NBMs and make it senseless effort.
reason2: it's too late to integrate that in '5.0' release, you had to ask for
that six months ago.

Marking RESOLVED INVALID as only the first issue makes sense and it's Cretor's
internal issue => not @nb.org. Request to get it fixed in Creator's buildsystem.