Community
Participate
Working Groups
Build Identifier: M20100909-0800 The existing Launch Configuration Migrate feature allows the user to click a Migrate button from the Global Settings to see a list of potential migration candidates. The drawback is that the user has no idea if he has a migration candidate unless he performs this step (thus likely to be overlooked) or the launch provider provides some mechanism for handling the situation. Reproducible: Always
Created attachment 182079 [details] Implementation that shows migration candidates as Problems. The patch adds a new combo box to the Launch Configurations global prefs allowing the user to select a behavior for migration candidates. Available behaviors are 1) ignore, 2) display as Info Problem, 3) display as Warning Problem, 4) display as Error Problem, and 5) automatically migrate. A QuickFix is provided for handling the Problems.
Created attachment 182081 [details] Screenshot of Global Prefs page
Created attachment 182082 [details] Screenshot of QuickFix dialog
Created attachment 182527 [details] UPDATE: Implementation that shows migration candidates as Problems. I updated the patch to fix a problem where the Restore Defaults buttons didn't work for the migration behavior combo. Also removed some redundant code.
Created attachment 183235 [details] UPDATE 2: Implementation that shows migration candidates as Problems. Patch 3 includes the following changes: 1. Reduced probability of deadlock for automatic launch config migration. 2. Handle read-only launch config migration candidates, though only for shared and not for local. 3. Show migration candidacy in Launch Config dialog.
Pretty cool. Can we find time to review the 413 loc patch?
(In reply to comment #6) > Pretty cool. Can we find time to review the 413 loc patch? Sadly the CQ deadline has passed (it was around Feb 3rd), a patch of this size will have to wait until the next release...
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
