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 110287 - Uninstall more gems in batch mode
Summary: Uninstall more gems in batch mode
Status: RESOLVED WONTFIX
Alias: None
Product: ruby
Classification: Unclassified
Component: Gems (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Erno Mononen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-19 13:52 UTC by Martin Krauskopf
Modified: 2009-12-21 06:04 UTC (History)
0 users

See Also:
Issue Type: DEFECT
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 Martin Krauskopf 2007-07-19 13:52:25 UTC 
When more gems is uninstalled at once there is one "Success" dialog per gem which is little annoying. Would be nicer to
have one dialog on the end of uninstallation of all gems.
Comment 1 Torbjorn Norbye 2007-07-19 15:30:25 UTC 
That's because "gem uninstall" only allows a single gem to be uninstalled at one time, so my batch-mode uninstall simply iterates over the selected items and 
calls gem uninstall on each (which means a separate ruby subprocess each, which is why you get separate confirmation dialogs). I can fix this by modifying 
the gem handler such that it accumulates output from different processes to hide this distinction from the user - but this is why this wasn't just done right 
away the way it is for "gem install" (which -does- let me specify a list of gems to be installed in one shot).
Comment 2 Martin Krauskopf 2008-03-14 19:59:11 UTC 
Likely possible with our_uninstall.rb file using RubyGems API (note for me).
Comment 3 Quality Engineering 2009-12-21 06:04:45 UTC 
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. 

We apologize for any inconvenience.


Thank you.
The NetBeans Team