Community
Participate
Working Groups
The methods below call IRunnableContext.run(boolean fork, boolean cancelable, IRunnableWithProgress runnable) with run(false, *, *). When fork is set to false then the UI looks frozen for long operations: only the progress monitor is updated while the rest of the UI is not. We must only use fork=false if there would be a threading problem with fork=true. Please revisit your methods from the list below. AddGetterSetter.run AddImportOnSelectionAction.addImport AddMethodStubAction.run AddUnimplementedMethodsAction.run CopyAction.processElements FileTransferDropAdapter.drop JDIAttachLauncherWizard.performFinish JavaApplicationWizard.performFinish LaunchWizardDialog.nextPressed NewElementWizardPage.invokeRunnable OrganizeImportsAction.run RefactoringWizard.performFinish SearchManager.removeAllSearches SearchManager.setCurrentSearch SearchPage.ensureIndexIsUpdated SourceAttachmentPropertyPage.performOk TextEditor.doSaveAs UndoManager.run VCMAction.run Workbench.disconnectFromWorkspace NOTES:
moved to 'active'
PRODUCT VERSION: Jabiru 106+
not for 2.0
We should check this during 2.1 pass and then close the PR
Chaning state from assigned later to resolved later. Assigned later got introduced by the last bug conversion and is not a supported Eclipse bug state.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.