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 141696 - [65cat] Terminate gem fetching operation when platform is changed in Gem Panel
Summary: [65cat] Terminate gem fetching operation when platform is changed in Gem Panel
Status: NEW
Alias: None
Product: ruby
Classification: Unclassified
Component: Gems (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@ruby
Depends on:
Reported: 2008-07-25 16:03 UTC by esmithbss
Modified: 2011-01-28 20:12 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description esmithbss 2008-07-25 16:03:19 UTC
When fetching the Gems for the GemPanel, it is possible to switch platforms in the platform list.  

When this happens, the IDE spawns a second process to fetch the gems of the updated platform, but gem fetching for the
original platform in the background continues until completion, whether or not it applies to the state of the Gem Panel.  

This can be confusing if either operation generates an error.

It would be beneficial to have the original gem request terminated prior to starting the second platform's gem fetching
Comment 1 Martin Krauskopf 2008-07-28 13:04:29 UTC
Hard to say. The bug is not that the spawned process is not killed since it prepares the gems for the case you switch
back to the platform previously selected (in this or the next Gem Manager session). You should not see errors for other
platform then currently selected. If you switch to other one and the update of previously selected one ends up with
errors it should not bothers you. That would be a bug.

But the behavior you described is probably still the best one. No need to pre-cache gem for platform which was deselected.

This part still needs some clean-up, after last-week overhaul. Might be for 6.5, not sure about Target Milestone yet.