-
Interfaces Interface Description org.eclipse.compare.IStreamMerger Clients should useorg.eclipse.team.core.mapping.IStorageMergerinstead.org.eclipse.core.filebuffers.IDocumentFactory As of 3.2 the"org.eclipse.core.filebuffers.documentCreation"extension point has been deprecated. See the extension point documentation for more details.org.eclipse.core.resources.IFileModificationValidator clients should subclassFileModificationValidatorinstead of implementing this interfaceorg.eclipse.core.runtime.ILibrary In Eclipse 3.0 the plug-in classpath representation was changed. Clients ofILibraryare directed to the headers associated with the relevant bundle. In particular, theBundle-Classpathheader contains all available information about the classpath of a plug-in. Having retrieved the header, theManifestElementhelper class can be used to parse the value and discover the individual class path entries. The various header attributes are defined inConstants.For example,
String header = bundle.getHeaders().get(Constants.BUNDLE_CLASSPATH); ManifestElement[] elements = ManifestElement.parseHeader( Constants.BUNDLE_CLASSPATH, header); if (elements == null) return; elements[0].getValue(); // the jar/dir containing the code ...Note that this new structure does not include information on which packages are exported or present in the listed classpath entries. This information is no longer relevant.
See
IPluginDescriptorfor information on the relationship between plug-in descriptors and bundles.This interface must only be used by plug-ins which explicitly require the org.eclipse.core.runtime.compatibility plug-in.
org.eclipse.core.runtime.IPlatformRunnable useIApplicationorg.eclipse.core.runtime.IPluginDescriptor org.eclipse.core.runtime.IPluginPrerequisite In Eclipse 3.0 the plug-in prerequisite representation was changed. Clients ofIPluginPrerequisiteare directed to the headers associated with the relevant bundle. In particular, theRequire-Bundleheader contains all available information about the prerequisites of a plug-in. Having retrieved the header, theManifestElementhelper class can be used to parse the value and discover the individual prerequisite plug-ins. The various header attributes are defined inConstants.For example,
String header = bundle.getHeaders().get(Constants.REQUIRE_BUNDLE); ManifestElement[] elements = ManifestElement.parseHeader( Constants.REQUIRE_BUNDLE, header); if (elements == null) return; elements[0].getValue(); // the prerequisite plug-in id elements[0].getAttribute(Constants.BUNDLE_VERSION_ATTRIBUTE); // the prerequisite plug-in version ...See
IPluginDescriptorfor information on the relationship between plug-in descriptors and bundles.This interface must only be used by plug-ins which explicitly require the org.eclipse.core.runtime.compatibility plug-in.
org.eclipse.core.runtime.IPluginRegistry org.eclipse.debug.core.model.IFilteredStep clients should implementIStepFiltersinsteadorg.eclipse.debug.ui.console.IConsoleHyperlink replaced by org.eclipse.ui.console.IHyperlinkorg.eclipse.e4.ui.model.application.ui.basic.MDialog org.eclipse.e4.ui.model.application.ui.basic.MInputPart Use Part instead.org.eclipse.e4.ui.model.application.ui.basic.MWizardDialog org.eclipse.e4.ui.model.application.ui.MInput No longer usedorg.eclipse.e4.ui.workbench.UIEvents.Input org.eclipse.equinox.p2.query.IMatchQuery If possible, use one of the predefined queries inQueryUtilor use theQueryUtil.createMatchQuery(String, Object...)to create a custom expression based query. If the query cannot be expressed using the p2QL, then use a predefined or custom expression query as a first filter (in worst case, useQueryUtil.createIUAnyQuery()) and then provide further filtering like so:for(iter = queryable.query(someExpressionQuery).iterator(); iter.hasNext();) { // do your match here }org.eclipse.help.IHelp marked for deletion, see Bug 442959. This interface became obsolete in 3.0, along with the extension point that it was associated with. The functionality provided by this interface is available elsewhere. UseHelpSystem.getTocs()andHelpSystem.getContext(String)to obtain help resources. Use various display methods ofIWorkbenchHelpSystemto display help resources.org.eclipse.jface.contentassist.ISubjectControlContentAssistant As of 3.2, replaced by Platform UI's field assist supportorg.eclipse.jface.contentassist.ISubjectControlContentAssistProcessor As of 3.2, replaced by Platform UI's field assist supportorg.eclipse.jface.contentassist.ISubjectControlContextInformationPresenter As of 3.2, replaced by Platform UI's field assist supportorg.eclipse.jface.contentassist.ISubjectControlContextInformationValidator As of 3.2, replaced by Platform UI's field assist supportorg.eclipse.jface.fieldassist.IControlCreator As of 3.3, clients should useControlDecorationinstead ofDecoratedField.org.eclipse.jface.text.IAutoIndentStrategy since 3.0, useIAutoEditStrategydirectlyorg.eclipse.jface.text.ITextViewerExtension3 replaced byITextViewerExtension5org.eclipse.search.ui.IActionGroupFactory Part of the old ('classic') search result view. Since 3.0 clients can create their own search result view pages (seeISearchResultPage), leaving it up to the page how to create actions.org.eclipse.search.ui.IContextMenuContributor Part of the old ('classic') search result view. Since 3.0 clients can create their own search result view pages (seeISearchResultPage), leaving it up to the page how to create actions in context menus.org.eclipse.search.ui.IGroupByKeyComputer Part of the old ('classic') search result view. Since 3.0 clients can create their own search result view pages (seeISearchResultPage), leaving it up to the page how to group search results.org.eclipse.search.ui.ISearchResultView Part of the old ('classic') search result view. Since 3.0 clients can create their own search result view pages. To access the parent view,ISearchResultViewPartis used instead.org.eclipse.search.ui.ISearchResultViewEntry Part of the old ('classic') search result view. Since 3.0 clients can create their own search result view pages (seeISearchResultPage), leaving it up to the search how to model search results.AbstractTextSearchResultandMatchcan be used to port old searches to the new API design.org.eclipse.team.core.IFileTypeInfo Use theIFileContentManagerAPI instead.org.eclipse.team.core.IProjectSetSerializer UseRepositoryProviderType.getProjectSetCapability()to obtain an instance ofProjectSetCapabilityinstead.org.eclipse.team.ui.ISaveableWorkbenchPart Clients should use a subclass ofCompareEditorInputandCompareUI.openCompareDialog(org.eclipse.compare.CompareEditorInput)org.eclipse.ui.commands.ICategory Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.commands.ICategoryListener Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.commands.ICommand Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.commands.ICommandListener Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.commands.ICommandManager Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.commands.ICommandManagerListener Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.commands.IHandler Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.commands.IHandlerListener Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.commands.IKeyConfiguration Please use the bindings support in the "org.eclipse.jface" plug-in instead.org.eclipse.ui.commands.IKeyConfigurationListener Please use the bindings support in the "org.eclipse.jface" plug-in instead.org.eclipse.ui.commands.IKeySequenceBinding Please use the bindings support in the "org.eclipse.jface" plug-in instead.org.eclipse.ui.commands.IWorkbenchCommandSupport Please useICommandServiceandIHandlerServiceinstead.org.eclipse.ui.contexts.IContext Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.contexts.IContextListener Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.contexts.IContextManager Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.contexts.IContextManagerListener Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.contexts.IWorkbenchContextSupport Please useIBindingServiceandIContextServiceinstead.org.eclipse.ui.editors.text.IEncodingActionsConstants As of 3.1, encoding needs to be changed via properties dialog. This interface is planned for removal after March 2021 (see bug#544309 for details).org.eclipse.ui.editors.text.IEncodingActionsDefinitionIds As of 3.1, encoding needs to be changed via properties dialog. This interface is planned for removal after March 2021 (see bug#544309 for details).org.eclipse.ui.editors.text.IEncodingActionsHelpContextIds As of 3.1, encoding needs to be changed via properties dialog. This interface is planned for removal after March 2021 (see bug#544309 for details).org.eclipse.ui.IActionDelegateWithEvent Use org.eclipse.ui.IActionDelegate2 instead.org.eclipse.ui.IKeyBindingService See IContextService to manage scopes and IHandlerService to manage handlers. IAction can be proxied by org.eclipse.jface.commands.ActionHandler.org.eclipse.ui.INestableKeyBindingService This is now handled byIServiceLocatorwhich can be nested.org.eclipse.ui.keys.IKeyFormatter Please use org.eclipse.jface.bindings.keys.IKeyFormatterorg.eclipse.ui.views.navigator.IResourceNavigator as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.update.configurator.IPlatformConfiguration The org.eclipse.update component has been replaced by Equinox p2. This API will be deleted in a future release. See bug 311590 for details.org.eclipse.update.configurator.IPlatformConfigurationFactory The org.eclipse.update component has been replaced by Equinox p2. This API will be deleted in a future release. See bug 311590 for details.
-
Classes Class Description org.eclipse.compare.EditionSelectionDialog Use anorg.eclipse.team.ui.history.IHistoryPageSourcein conjunction with theorg.eclipse.team.ui.history.IHistoryViewor aHistoryPageCompareEditorInput. For sub-file elements, aorg.eclipse.team.ui.history.ElementLocalHistoryPageSourcecan be used.org.eclipse.core.commands.util.Tracing org.eclipse.core.databinding.beans.BeansObservables useBeanPropertiesinsteadorg.eclipse.core.databinding.beans.PojoObservables usePojoPropertiesinsteadorg.eclipse.core.databinding.observable.map.BidirectionalMap This class is deprecated; useBidiObservableMapinstead.org.eclipse.core.databinding.observable.set.MappedSet This class is deprecated.org.eclipse.core.runtime.content.XMLRootElementContentDescriber UseXMLRootElementContentDescriber2insteadorg.eclipse.core.runtime.PluginVersionIdentifier clients should useVersioninsteadorg.eclipse.core.runtime.Preferences This class is replaced byIEclipsePreferences. Setting a default value is accomplished by a setting a value in theDefaultScope, and setting an explicit non-default value is accomplished by setting a value in theInstanceScope. To obtain a preference value, use the preference accessor methods onIPreferencesService.org.eclipse.core.runtime.SubProgressMonitor useSubMonitorinsteadorg.eclipse.debug.ui.actions.LaunchAsAction The use of perspective based launch shortcuts has been deprecated in the 3.1 release. Instead, selection sensitive launch is supported in the top level menus. UseLaunchShorcutsActioninstead.org.eclipse.debug.ui.actions.RulerBreakpointTypesActionDelegate Should use BreakpointTypesContribution instead.org.eclipse.debug.ui.DebugElementWorkbenchAdapter Custom content in the debug views is no longer supported byIWorkbenchAdapter. Custom content is currently supported by a provisional internal viewer framework.org.eclipse.debug.ui.DeferredDebugElementWorkbenchAdapter deferred custom content in the debug views is no longer supported byIDeferredWorkbenchAdapter. Deferred custom content is currently supported by a provisional internal viewer framework.org.eclipse.equinox.http.servlet.HttpServiceMultipartServlet No longer required.org.eclipse.equinox.p2.query.MatchQuery If possible, use one of the predefined queries inQueryUtilor use theQueryUtil.createMatchQuery(String, Object...)to create a custom expression based query. If the query cannot be expressed using the p2QL, then use a predefined or custom expression query as a first filter (in worst case, useQueryUtil.createIUAnyQuery()) and then provide further filtering like so:for(iter = queryable.query(someExpressionQuery).iterator(); iter.hasNext();) { // do your match here }org.eclipse.jface.contentassist.AbstractControlContentAssistSubjectAdapter As of 3.2, replaced by Platform UI's field assist supportorg.eclipse.jface.contentassist.ComboContentAssistSubjectAdapter As of 3.2, replaced by Platform UI's field assist supportorg.eclipse.jface.contentassist.SubjectControlContentAssistant As of 3.2, replaced by Platform UI's field assist support *org.eclipse.jface.contentassist.SubjectControlContextInformationValidator As of 3.2, replaced by Platform UI's field assist supportorg.eclipse.jface.contentassist.TextContentAssistSubjectAdapter As of 3.2, replaced by Platform UI's field assist supportorg.eclipse.jface.databinding.swt.SWTObservables org.eclipse.jface.dialogs.AnimatorFactory as of 3.3, this class is no longer used.org.eclipse.jface.fieldassist.DecoratedField As of 3.3, clients should useControlDecorationinstead.org.eclipse.jface.fieldassist.FieldAssistColors As of 3.3, this class is no longer necessary.org.eclipse.jface.fieldassist.TextControlCreator As of 3.3, clients should useControlDecorationinstead ofDecoratedField.org.eclipse.jface.text.Assert As of 3.3, replaced byAssertorg.eclipse.jface.text.DefaultAutoIndentStrategy since 3.1 useDefaultIndentLineAutoEditStrategyinsteadorg.eclipse.jface.text.DefaultUndoManager As of 3.2, replaced byTextViewerUndoManagerorg.eclipse.jface.text.PropagatingFontFieldEditor since 3.0 not longer in use, no longer supportedorg.eclipse.jface.text.rules.DefaultPartitioner As of 3.1, replaced byFastPartitionerinsteadorg.eclipse.jface.text.rules.RuleBasedDamagerRepairer useDefaultDamagerRepairerorg.eclipse.jface.text.rules.RuleBasedPartitioner useFastPartitionerinsteadorg.eclipse.jface.text.SequentialRewriteTextStore since 3.3 asGapTextStoreperforms better even for sequential rewrite scenariosorg.eclipse.jface.text.source.AnnotationBarHoverManager.Closer As of 3.4, no longer used as closer from super class is usedorg.eclipse.jface.text.source.AnnotationColumn useAnnotationRulerColumn(int)instead.org.eclipse.jface.text.source.AnnotationPainter.SquigglesStrategy As of 3.4, replaced byAnnotationPainter.UnderlineStrategyorg.eclipse.jface.text.templates.ContextTypeRegistry SeeContextTypeRegistryorg.eclipse.jface.text.templates.persistence.TemplatePersistenceData SeeTemplatePersistenceDataorg.eclipse.jface.text.templates.persistence.TemplateReaderWriter SeeTemplateReaderWriterorg.eclipse.jface.util.Assert As of 3.3, replaced byAssertorg.eclipse.jface.viewers.ViewerSorter useViewerComparatorinstead.org.eclipse.ltk.ui.refactoring.RedoRefactoringAction This action is now longer needed. Undo is now performed via the global undo/redo stack provided byorg.eclipse.core.commands.org.eclipse.ltk.ui.refactoring.UndoRefactoringAction This action is now longer needed. Undo is now performed via the global undo/redo stack provided byorg.eclipse.core.commands.org.eclipse.osgi.framework.eventmgr.EventListeners As of 3.5. Replaced by CopyOnWriteIdentityMap.org.eclipse.search.ui.SearchUI Part of the old ('classic') search. Since 3.0 clients can create their own search result view pages and useNewSearchUIinstead.org.eclipse.swt.custom.AnimatedProgress As of Eclipse 2.1, use ProgressBar with the style SWT.INDETERMINATE- Styles:
- VERTICAL, HORIZONTAL, BORDER
org.eclipse.swt.custom.TableTree As of 3.1 use Tree, TreeItem and TreeColumnorg.eclipse.swt.custom.TableTreeEditor As of 3.1 use TreeEditor with Tree, TreeItem and TreeColumnorg.eclipse.swt.custom.TableTreeItem As of 3.1 use Tree, TreeItem and TreeColumnorg.eclipse.team.ui.history.HistoryPageSaveablePart org.eclipse.team.ui.PageSaveablePart Clients should use a subclass ofCompareEditorInputandCompareUI.openCompareDialog(org.eclipse.compare.CompareEditorInput)org.eclipse.team.ui.SaveablePartAdapter Clients should use a subclass ofCompareEditorInputandCompareUI.openCompareDialog(org.eclipse.compare.CompareEditorInput)org.eclipse.team.ui.SaveablePartDialog Clients should use a subclass ofCompareEditorInputandCompareUI.openCompareDialog(org.eclipse.compare.CompareEditorInput)org.eclipse.team.ui.synchronize.ParticipantPageDialog org.eclipse.team.ui.synchronize.ParticipantPageSaveablePart Clients should use a subclass ofPageCompareEditorInputandCompareUI.openCompareDialog(org.eclipse.compare.CompareEditorInput)org.eclipse.ui.actions.CreateFileAction should use NewWizardMenu to populate a New submenu instead (see Navigator view)org.eclipse.ui.actions.CreateFolderAction should use NewWizardMenu to populate a New submenu instead (see Navigator view)org.eclipse.ui.actions.OpenNewPageMenu Workbench no longer exposes the concept of "pages" in the user ui model. See IWorkbench.showPerspective methods.org.eclipse.ui.actions.OpenNewWindowMenu See IWorkbench.showPerspective methods.org.eclipse.ui.actions.OpenPerspectiveMenu See IWorkbench.showPerspective methods.org.eclipse.ui.actions.QuickStartAction the IDE now uses the new intro mechanismorg.eclipse.ui.actions.ScrubLocalAction This class is obsolete; there is no support in the workspace for scrubbing local content.org.eclipse.ui.commands.AbstractHandler Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.commands.ActionHandler Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.commands.CategoryEvent Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.commands.CommandEvent Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.commands.CommandManagerEvent Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.commands.HandlerEvent Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.commands.HandlerSubmission Please useIHandlerService.activateHandlerinstead.org.eclipse.ui.commands.KeyConfigurationEvent Please use the bindings support in the "org.eclipse.jface" plug-in instead.org.eclipse.ui.commands.Priority This concept is now captured in theISourcesinteger constants.org.eclipse.ui.contentassist.ContentAssistHandler As of 3.2, replaced by JFace field assist supportorg.eclipse.ui.contexts.ContextEvent Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.contexts.ContextManagerEvent Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.contexts.EnabledSubmission Please useIContextService.activateContextinstead.org.eclipse.ui.dialogs.FileSelectionDialog Use org.eclipse.swt.widgets.FileDialog,org.eclipse.ui.dialogs.WizardExportPage use WizardExportResourcePageorg.eclipse.ui.dialogs.WizardImportPage use WizardResourceImportPageorg.eclipse.ui.dialogs.YesNoCancelListSelectionDialog Providing Cancel in addition to Yes/No is confusing. It is better to subclass the regular ListSelectionDialog, which uses OK/Cancel, and provide a separate checkbox if necessary.org.eclipse.ui.editors.text.EncodingActionGroup As of 3.1, encoding needs to be changed via properties dialog. This class is planned for removal after March 2021 (see bug#544309 for details).org.eclipse.ui.editors.text.TextEditorPreferencePage As of 2.1, fonts are managed by the workbench, no longer supportedorg.eclipse.ui.editors.text.TextFileDocumentProvider.NullProvider As of 3.3 - do not useorg.eclipse.ui.fieldassist.ContentAssistField As of 3.3, clients should useControlDecorationandContentAssistCommandAdapterinstead of this class.org.eclipse.ui.keys.CharacterKey Please use org.eclipse.jface.bindings.keys.KeyStroke and org.eclipse.jface.bindings.keys.KeyLookupFactoryorg.eclipse.ui.keys.Key Please use org.eclipse.jface.bindings.keys.KeyStroke and org.eclipse.jface.bindings.keys.KeyLookupFactoryorg.eclipse.ui.keys.KeyFormatterFactory Please use org.eclipse.jface.bindings.keys.KeyFormatterFactoryorg.eclipse.ui.keys.KeySequence Please use org.eclipse.jface.bindings.keys.KeySequenceorg.eclipse.ui.keys.KeyStroke Please use org.eclipse.jface.bindings.keys.KeyStrokeorg.eclipse.ui.keys.ModifierKey Please use org.eclipse.jface.bindings.keys.KeyStroke and org.eclipse.jface.bindings.keys.KeyLookupFactoryorg.eclipse.ui.keys.NaturalKey Please use org.eclipse.jface.bindings.keys.KeyStroke and org.eclipse.jface.bindings.keys.KeyLookupFactoryorg.eclipse.ui.keys.SpecialKey Please use org.eclipse.jface.bindings.keys.KeyStroke and org.eclipse.jface.bindings.keys.KeyLookupFactoryorg.eclipse.ui.keys.SWTKeySupport Please useSWTKeySupportorg.eclipse.ui.model.WorkbenchViewerSorter as of 3.3, useWorkbenchViewerComparatorinsteadorg.eclipse.ui.part.MultiPageEditor Use the classMultiPageEditorPartinsteadorg.eclipse.ui.texteditor.ConvertLineDelimitersAction since 3.1. Line delimiter conversion has been modified to work on groups of files rather than being editor specificorg.eclipse.ui.texteditor.ImageUtilities As of 3.0, replaced byImageUtilitiesorg.eclipse.ui.texteditor.InfoForm since 3.0. there is no replacement, use org.eclipse.ui.forms to define a component with a similar look and function.org.eclipse.ui.texteditor.MarkerRulerInfoAction useMarkerRulerActioninsteadorg.eclipse.ui.texteditor.PropagatingFontFieldEditor no longer supportedorg.eclipse.ui.texteditor.SaveAction As of 3.5, replaced byActionFactory.SAVEorg.eclipse.ui.texteditor.SelectMarkerRulerInfoAction As of 2.1, replaced bySelectMarkerRulerActionorg.eclipse.ui.texteditor.WorkbenchChainedTextFontFieldEditor since 3.0 not longer in use, no longer supported, use aChainedPreferenceStoreto access preferences from theorg.eclipse.ui.editorsplug-in.org.eclipse.ui.views.bookmarkexplorer.BookmarkNavigator This view is no longer in use as of Eclipse 3.4. The view referenced byIPageLayout.ID_BOOKMARKSis anExtendedMarkersView.org.eclipse.ui.views.navigator.CollapseAllAction as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.FilterSelectionAction as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.GotoActionGroup as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.GotoResourceAction as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.LocalSelectionTransfer as of 3.5, useLocalSelectionTransferinsteadorg.eclipse.ui.views.navigator.MainActionGroup as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.NavigatorDragAdapter as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.NavigatorDropAdapter as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.NavigatorFrameSource as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.OpenActionGroup as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.RefactorActionGroup as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.ResourceNavigator as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.ResourceNavigatorAction as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.ResourceNavigatorActionGroup as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.ResourceNavigatorMessages These messages are not API and should not be referenced outside of this plug-in.org.eclipse.ui.views.navigator.ResourceNavigatorMoveAction as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.ResourceNavigatorRenameAction as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.ResourcePatternFilter as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.ResourceSelectionUtil as of 3.5, useResourceSelectionUtilinstead.org.eclipse.ui.views.navigator.ResourceSorter as of 3.3, useResourceComparatorinsteadorg.eclipse.ui.views.navigator.ShowInNavigatorAction as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.SortAndFilterActionGroup as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.SortViewAction as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.ToggleLinkingAction as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.ui.views.navigator.WorkspaceActionGroup as of 3.5, use the Common Navigator Framework classes insteadorg.eclipse.update.configurator.ConfiguratorUtils The org.eclipse.update component has been replaced by Equinox p2. This API will be deleted in a future release. See bug 311590 for details.
-
Exceptions Exceptions Description org.eclipse.ui.commands.CommandException Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.commands.ExecutionException Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.commands.NotDefinedException Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.commands.NotHandledException Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.contexts.ContextException Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.contexts.NotDefinedException Please use the "org.eclipse.core.commands" plug-in instead.org.eclipse.ui.keys.ParseException Please use org.eclipse.jface.bindings.keys.ParseExceptionorg.eclipse.ui.texteditor.ValidateStateException No longer used, create aCoreExceptioninstead