|
Eclipse Platform Release 3.4 |
||||||||||
| PREV NEXT | FRAMES NO FRAMES | ||||||||||
| Deprecated Classes | |
| org.eclipse.jface.contentassist.AbstractControlContentAssistSubjectAdapter
As of 3.2, replaced by Platform UI's field assist support |
|
| 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.swt.custom.AnimatedProgress
As of Eclipse 2.1, use ProgressBar with the style SWT.INDETERMINATE
|
|
| org.eclipse.jface.dialogs.AnimatorFactory
as of 3.3, this class is no longer used. |
|
| org.eclipse.jface.text.source.AnnotationBarHoverManager.Closer
As of 3.4, no longer used as closer from super class is used |
|
| org.eclipse.jface.text.source.AnnotationColumn
use AnnotationRulerColumn instead. |
|
| org.eclipse.jface.text.source.AnnotationPainter.SquigglesStrategy
As of 3.4, replaced by AnnotationPainter.UnderlineStrategy |
|
| org.eclipse.jface.text.Assert
As of 3.3, replaced by Assert |
|
| org.eclipse.jface.util.Assert
As of 3.3, replaced by Assert
|
|
| org.eclipse.ui.views.bookmarkexplorer.BookmarkNavigator
This view is no longer in use as of Eclipse 3.4. The view referenced by IPageLayout.ID_BOOKMARKS is an ExtendedMarkersView.
|
|
| org.eclipse.ui.commands.CategoryEvent
Please use the "org.eclipse.core.commands" plug-in instead. |
|
| org.eclipse.ui.keys.CharacterKey
Please use org.eclipse.jface.bindings.keys.KeyStroke and org.eclipse.jface.bindings.keys.KeyLookupFactory |
|
| org.eclipse.jface.contentassist.ComboContentAssistSubjectAdapter
As of 3.2, replaced by Platform UI's field assist support |
|
| 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.core.runtime.model.ConfigurationElementModel
In Eclipse 3.0 the runtime was refactored and all non-essential elements removed. This class provides facilities primarily intended for tooling. As such it has been removed and no directly substitutable API provided. |
|
| org.eclipse.core.runtime.model.ConfigurationPropertyModel
In Eclipse 3.0 the runtime was refactored and all non-essential elements removed. This class provides facilities primarily intended for tooling. As such it has been removed and no directly substitutable API provided. |
|
| org.eclipse.ui.fieldassist.ContentAssistField
As of 3.3, clients should use ControlDecoration and
ContentAssistCommandAdapter instead of this class. |
|
| org.eclipse.ui.contentassist.ContentAssistHandler
As of 3.2, replaced by JFace field assist support |
|
| org.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.texteditor.ConvertLineDelimitersAction
since 3.1. Line delimiter conversion has been modified to work on groups of files rather than being editor specific |
|
| 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.debug.ui.DebugElementWorkbenchAdapter
Custom content in the debug views is no longer supported by IWorkbenchAdapter. Custom content is currently supported
by a provisional internal viewer framework. |
|
| org.eclipse.jface.fieldassist.DecoratedField
As of 3.3, clients should use ControlDecoration instead. |
|
| org.eclipse.jface.text.DefaultAutoIndentStrategy
since 3.1 use DefaultIndentLineAutoEditStrategy instead |
|
| org.eclipse.jface.text.rules.DefaultPartitioner
As of 3.1, replaced by FastPartitioner instead |
|
| org.eclipse.jface.text.DefaultUndoManager
As of 3.2, replaced by TextViewerUndoManager |
|
| org.eclipse.debug.ui.DeferredDebugElementWorkbenchAdapter
deferred custom content in the debug views is no longer supported by IDeferredWorkbenchAdapter. Deferred custom content is currently supported
by a provisional internal viewer framework. |
|
| org.eclipse.ui.help.DialogPageContextComputer
nested contexts are no longer supported by the help support system |
|
| org.eclipse.compare.EditionSelectionDialog
Use an org.eclipse.team.ui.history.IHistoryPageSource in conjunction with
the org.eclipse.team.ui.history.IHistoryView or a HistoryPageCompareEditorInput.
For sub-file elements, a org.eclipse.team.ui.history.ElementLocalHistoryPageSource can be used. |
|
| org.eclipse.ui.contexts.EnabledSubmission
Please use IContextService.activateContext
instead. |
|
| org.eclipse.ui.editors.text.EncodingActionGroup
As of 3.1, encoding needs to be changed via properties dialog |
|
| org.eclipse.core.runtime.model.ExtensionModel
In Eclipse 3.0 the runtime was refactored and all non-essential elements removed. This class provides facilities primarily intended for tooling. As such it has been removed and no directly substitutable API provided. |
|
| org.eclipse.core.runtime.model.ExtensionPointModel
In Eclipse 3.0 the runtime was refactored and all non-essential elements removed. This class provides facilities primarily intended for tooling. As such it has been removed and no directly substitutable API provided. |
|
| org.eclipse.core.runtime.model.Factory
In Eclipse 3.0 the runtime was refactored and all non-essential elements removed. This class provides facilities primarily intended for tooling. As such it has been removed and no directly substitutable API provided. |
|
| org.eclipse.jface.fieldassist.FieldAssistColors
As of 3.3, this class is no longer necessary. |
|
| org.eclipse.ui.dialogs.FileSelectionDialog
Use org.eclipse.swt.widgets.FileDialog, |
|
| org.eclipse.ui.commands.HandlerEvent
Please use the "org.eclipse.core.commands" plug-in instead. |
|
| org.eclipse.ui.commands.HandlerSubmission
Please use IHandlerService.activateHandler
instead. |
|
| org.eclipse.team.ui.history.HistoryPageSaveablePart
use HistoryPageCompareEditorInput |
|
| org.eclipse.jface.dialogs.ImageAndMessageArea
As of 3.3, this class is no longer necessary. |
|
| org.eclipse.ui.texteditor.ImageUtilities
As of 3.0, replaced by ImageUtilities |
|
| org.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.keys.Key
Please use org.eclipse.jface.bindings.keys.KeyStroke and org.eclipse.jface.bindings.keys.KeyLookupFactory |
|
| org.eclipse.ui.commands.KeyConfigurationEvent
Please use the bindings support in the "org.eclipse.jface" plug-in instead. |
|
| org.eclipse.ui.keys.KeyFormatterFactory
Please use org.eclipse.jface.bindings.keys.KeyFormatterFactory |
|
| org.eclipse.ui.keys.KeySequence
Please use org.eclipse.jface.bindings.keys.KeySequence |
|
| org.eclipse.ui.keys.KeyStroke
Please use org.eclipse.jface.bindings.keys.KeyStroke |
|
| org.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. Use LaunchShorcutsAction instead. |
|
| org.eclipse.core.runtime.model.LibraryModel
In Eclipse 3.0 the runtime was refactored and all non-essential elements removed. This class provides facilities primarily intended for tooling. As such it has been removed and no directly substitutable API provided. |
|
| org.eclipse.jface.util.ListenerList
Please use ListenerList instead.
Please note that the ListenerList.ListenerList(int) and
ListenerList.ListenerList(int)
constructors have different semantics. Please read the javadoc
carefully. Also note that the equivalent of
ListenerList.ListenerList() is actually
ListenerList.ListenerList(int)
with ListenerList.IDENTITY as
the argument. |
|
| org.eclipse.ui.texteditor.MarkerRulerInfoAction
use MarkerRulerAction instead |
|
| org.eclipse.ui.keys.ModifierKey
Please use org.eclipse.jface.bindings.keys.KeyStroke and org.eclipse.jface.bindings.keys.KeyLookupFactory |
|
| org.eclipse.ui.part.MultiPageEditor
Use the class MultiPageEditorPart instead |
|
| org.eclipse.ui.keys.NaturalKey
Please use org.eclipse.jface.bindings.keys.KeyStroke and org.eclipse.jface.bindings.keys.KeyLookupFactory |
|
| 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.team.ui.PageSaveablePart
Clients should use a subclass of CompareEditorInput
and CompareUI.openCompareDialog(org.eclipse.compare.CompareEditorInput) |
|
| org.eclipse.team.ui.synchronize.ParticipantPageDialog
Clients should use ParticipantPageCompareEditorInput
and CompareUI.openCompareDialog(org.eclipse.compare.CompareEditorInput) |
|
| org.eclipse.team.ui.synchronize.ParticipantPageSaveablePart
Clients should use a subclass of PageCompareEditorInput
and CompareUI.openCompareDialog(org.eclipse.compare.CompareEditorInput) |
|
| org.eclipse.core.runtime.model.PluginDescriptorModel
In Eclipse 3.0 the runtime was refactored and all non-essential elements removed. This class provides facilities primarily intended for tooling. As such it has been removed and no directly substitutable API provided. |
|
| org.eclipse.core.runtime.model.PluginFragmentModel
In Eclipse 3.0 the runtime was refactored and all non-essential elements removed. This class provides facilities primarily intended for tooling. As such it has been removed and no directly substitutable API provided. |
|
| org.eclipse.core.runtime.model.PluginModel
In Eclipse 3.0 the runtime was refactored and all non-essential elements removed. This class provides facilities primarily intended for tooling. As such it has been removed and no directly substitutable API provided. |
|
| org.eclipse.core.runtime.model.PluginModelObject
In Eclipse 3.0 the runtime was refactored and all non-essential elements removed. This class provides facilities primarily intended for tooling. As such it has been removed and no directly substitutable API provided. |
|
| org.eclipse.core.runtime.model.PluginPrerequisiteModel
In Eclipse 3.0 the runtime was refactored and all non-essential elements removed. This class provides facilities primarily intended for tooling. As such it has been removed and no directly substitutable API provided. |
|
| org.eclipse.core.runtime.model.PluginRegistryModel
In Eclipse 3.0 the runtime was refactored and all non-essential elements removed. This class provides facilities primarily intended for tooling. As such it has been removed and no directly substitutable API provided. |
|
| org.eclipse.core.runtime.PluginVersionIdentifier
clients should use Version instead |
|
| org.eclipse.ui.commands.Priority
This concept is now captured in the ISources
integer constants. |
|
| org.eclipse.jface.text.PropagatingFontFieldEditor
since 3.0 not longer in use, no longer supported |
|
| org.eclipse.ui.texteditor.PropagatingFontFieldEditor
no longer supported |
|
| org.eclipse.ui.actions.QuickStartAction
the IDE now uses the new intro mechanism |
|
| org.eclipse.ltk.ui.refactoring.RedoRefactoringAction
This action is now longer needed. Undo is now performed via the global undo/redo stack provided by org.eclipse.core.commands. |
|
| org.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.ResourceSorter
as of 3.3, use ResourceComparator instead |
|
| org.eclipse.jface.text.rules.RuleBasedDamagerRepairer
use DefaultDamagerRepairer |
|
| org.eclipse.jface.text.rules.RuleBasedPartitioner
use FastPartitioner instead |
|
| org.eclipse.team.ui.SaveablePartAdapter
Clients should use a subclass of CompareEditorInput
and CompareUI.openCompareDialog(org.eclipse.compare.CompareEditorInput) |
|
| org.eclipse.team.ui.SaveablePartDialog
Clients should use a subclass of CompareEditorInput
and CompareUI.openCompareDialog(org.eclipse.compare.CompareEditorInput) |
|
| org.eclipse.ui.actions.ScrubLocalAction
This class is obsolete; there is no support in the workspace for scrubbing local content. |
|
| org.eclipse.search.ui.SearchUI
Part of the old ('classic') search. Since 3.0 clients can create their own search result view pages and use NewSearchUI instead. |
|
| org.eclipse.ui.texteditor.SelectMarkerRulerInfoAction
As of 2.1, replaced by SelectMarkerRulerAction |
|
| org.eclipse.jface.text.SequentialRewriteTextStore
since 3.3 as GapTextStore performs better even for sequential rewrite scenarios |
|
| org.eclipse.ui.keys.SpecialKey
Please use org.eclipse.jface.bindings.keys.KeyStroke and org.eclipse.jface.bindings.keys.KeyLookupFactory |
|
| org.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 support |
|
| org.eclipse.ui.keys.SWTKeySupport
Please use org.eclipse.jface.bindings.keys.SWTKeySupport |
|
| org.eclipse.swt.custom.TableTree
As of 3.1 use Tree, TreeItem and TreeColumn |
|
| org.eclipse.swt.custom.TableTreeEditor
As of 3.1 use TreeEditor with Tree, TreeItem and TreeColumn |
|
| org.eclipse.swt.custom.TableTreeItem
As of 3.1 use Tree, TreeItem and TreeColumn |
|
| org.eclipse.jface.viewers.TableTreeViewer
As of 3.1 use TreeViewer instead |
|
| org.eclipse.ui.views.tasklist.TaskList
This view is no longer in use as of Eclipse 3.4. The view referenced by IPageLayout.ID_TASK_LIST is an MarkerSupportView.
|
|
| org.eclipse.jface.contentassist.TextContentAssistSubjectAdapter
As of 3.2, replaced by Platform UI's field assist support |
|
| org.eclipse.jface.fieldassist.TextControlCreator
As of 3.3, clients should use ControlDecoration instead
of DecoratedField. |
|
| org.eclipse.ui.editors.text.TextEditorPreferencePage
As of 2.1, fonts are managed by the workbench, no longer supported |
|
| org.eclipse.ui.editors.text.TextFileDocumentProvider.NullProvider
since 3.3 - do not use |
|
| org.eclipse.ltk.ui.refactoring.UndoRefactoringAction
This action is now longer needed. Undo is now performed via the global undo/redo stack provided by org.eclipse.core.commands. |
|
| org.eclipse.core.runtime.model.URLModel
In Eclipse 3.0 the runtime was refactored and all non-essential elements removed. This class provides facilities primarily intended for tooling. As such it has been removed and no directly substitutable API provided. |
|
| org.eclipse.ui.help.ViewContextComputer
nested contexts are no longer supported by the help support system |
|
| org.eclipse.ui.dialogs.WizardExportPage
use WizardExportResourcePage |
|
| org.eclipse.ui.dialogs.WizardImportPage
use WizardResourceImportPage |
|
| org.eclipse.ui.texteditor.WorkbenchChainedTextFontFieldEditor
since 3.0 not longer in use, no longer supported, use a ChainedPreferenceStore to access preferences from the
org.eclipse.ui.editors plug-in. |
|
| org.eclipse.ui.help.WorkbenchHelp
clients should use IWorkbenchHelpSystem instead |
|
| org.eclipse.ui.model.WorkbenchViewerSorter
as of 3.3, use WorkbenchViewerComparator instead |
|
| org.eclipse.core.resources.WorkspaceLock
it is no longer possible to override the workspace lock behavior. This functionality is now provided in the platform API by implementing the org.eclipse.core.runtime.jobs.ILockListener interface. |
|
| org.eclipse.core.runtime.content.XMLRootElementContentDescriber
Use XMLRootElementContentDescriber2 instead |
|
| org.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. |
|
| Deprecated Interfaces | |
| org.eclipse.ui.IActionDelegateWithEvent
Use org.eclipse.ui.IActionDelegate2 instead. |
|
| org.eclipse.search.ui.IActionGroupFactory
Part of the old ('classic') search result view. Since 3.0 clients can create their own search result view pages (see ISearchResultPage), leaving it up to the page
how to create actions. |
|
| org.eclipse.jface.text.IAutoIndentStrategy
since 3.0, use IAutoEditStrategy directly |
|
| 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.debug.ui.console.IConsoleHyperlink
replaced by org.eclipse.ui.console.IHyperlink |
|
| org.eclipse.ui.contexts.IContext
Please use the "org.eclipse.core.commands" plug-in instead. |
|
| org.eclipse.ui.help.IContextComputer
nested contexts are no longer supported by the help support system |
|
| 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.search.ui.IContextMenuContributor
Part of the old ('classic') search result view. Since 3.0 clients can create their own search result view pages (see ISearchResultPage), leaving it up to the page
how to create actions in context menus. |
|
| org.eclipse.jface.fieldassist.IControlCreator
As of 3.3, clients should use ControlDecoration instead
of DecoratedField. |
|
| 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.ui.editors.text.IEncodingActionsConstants
As of 3.1, encoding needs to be changed via properties dialog |
|
| org.eclipse.ui.editors.text.IEncodingActionsDefinitionIds
As of 3.1, encoding needs to be changed via properties dialog |
|
| org.eclipse.ui.editors.text.IEncodingActionsHelpContextIds
As of 3.1, encoding needs to be changed via properties dialog |
|
| org.eclipse.core.resources.IFileModificationValidator
clients should subclass FileModificationValidator instead
of implementing this interface |
|
| org.eclipse.team.core.IFileTypeInfo
Use the IFileContentManager API instead. |
|
| org.eclipse.debug.core.model.IFilteredStep
clients should implement IStepFilters instead |
|
| 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 (see ISearchResultPage), leaving it up to the page
how to group search results. |
|
| 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.help.IHelp
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. Use HelpSystem.getTocs()
and
HelpSystem.getContext(String)
to obtain help resources. Use various display methods of
WorkbenchHelpto
display help resources. |
|
| org.eclipse.update.configuration.IInstallDeltaHandler
Do not use this interface. The extension point deltaHandler has been deprecated. |
|
| 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.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.keys.IKeyFormatter
Please use org.eclipse.jface.bindings.keys.IKeyFormatter |
|
| org.eclipse.ui.commands.IKeySequenceBinding
Please use the bindings support in the "org.eclipse.jface" plug-in instead. |
|
| org.eclipse.core.runtime.ILibrary
In Eclipse 3.0 the plug-in classpath representation was changed. Clients of ILibrary are directed to the headers associated with the relevant bundle.
In particular, the Bundle-Classpath header contains all available information
about the classpath of a plug-in. Having retrieved the header, the ManifestElement
helper class can be used to parse the value and discover the individual
class path entries. The various header attributes are defined in Constants.
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 This interface must only be used by plug-ins which explicitly require the org.eclipse.core.runtime.compatibility plug-in. |
|
| org.eclipse.ui.INestableKeyBindingService
This is now handled by IServiceLocator which can
be nested. |
|
| org.eclipse.core.runtime.IPlatformRunnable
use IApplication |
|
org.eclipse.core.runtime.IPluginDescriptor
IPluginDescriptor was refactored in Eclipse 3.0.
Most of the functionality has moved to Platform and the
plug-in descriptor has been replaced with the OSGi Bundle
object.
This interface must only be used by plug-ins which explicitly require the org.eclipse.core.runtime.compatibility plug-in.
For most uses the bundle object can be treated as an opaque token
representing your plug-in to the system -- It must be supplied to various
Clients of this interface have a reference to an
The resulting bundle object can be used
to carry out the adaptation steps outlined for each of the
|
|
| org.eclipse.core.runtime.IPluginPrerequisite
In Eclipse 3.0 the plug-in prerequisite representation was changed. Clients of IPluginPrerequisite are directed to the headers associated with the relevant bundle.
In particular, the Require-Bundle header contains all available information
about the prerequisites of a plug-in. Having retrieved the header, the ManifestElement
helper class can be used to parse the value and discover the individual
prerequisite plug-ins. The various header attributes are defined in Constants.
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 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
The plug-in registry has been generalized in Eclipse 3.0. It is now the IExtensionRegistry. Most of the IPluginRegistry function
is directly supported on the new interface without change. Most clients
of IPluginRegistry need only to change their references to use
IExtensionRegistry. The only exceptions are
methods that return IPluginDescriptors. See the relevant method
comments for details.
This interface must only be used by plug-ins which explicitly require the org.eclipse.core.runtime.compatibility plug-in. |
|
| org.eclipse.team.core.IProjectSetSerializer
Use RepositoryProviderType.getProjectSetCapability()
to obtain an instance of ProjectSetCapability instead. |
|
| org.eclipse.team.ui.ISaveableWorkbenchPart
Clients should use a subclass of CompareEditorInput
and CompareUI.openCompareDialog(org.eclipse.compare.CompareEditorInput) |
|
| 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, ISearchResultViewPart is 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 (see ISearchResultPage), leaving it up to the search
how to model search results. AbstractTextSearchResult and Match can be used to port old searches to the new API design. |
|
| org.eclipse.update.configuration.ISessionDelta
Do not use this interface |
|
| org.eclipse.compare.IStreamMerger
Clients should use org.eclipse.team.core.mapping.IStorageMerger instead. |
|
| org.eclipse.jface.contentassist.ISubjectControlContentAssistant
As of 3.2, replaced by Platform UI's field assist support |
|
| org.eclipse.jface.contentassist.ISubjectControlContentAssistProcessor
As of 3.2, replaced by Platform UI's field assist support |
|
| org.eclipse.jface.contentassist.ISubjectControlContextInformationPresenter
As of 3.2, replaced by Platform UI's field assist support |
|
| org.eclipse.jface.contentassist.ISubjectControlContextInformationValidator
As of 3.2, replaced by Platform UI's field assist support |
|
| org.eclipse.jface.text.ITextViewerExtension3
replaced by ITextViewerExtension5 |
|
| org.eclipse.ui.commands.IWorkbenchCommandSupport
Please use ICommandService and
IHandlerService instead. |
|
| org.eclipse.ui.contexts.IWorkbenchContextSupport
Please use IBindingService and
IContextService instead. |
|
| Deprecated Exceptions | |
| org.eclipse.ui.commands.CommandException
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.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.contexts.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.keys.ParseException
Please use org.eclipse.jface.bindings.keys.ParseException |
|
| org.eclipse.ui.texteditor.ValidateStateException
|
|