Overview | Package | Class | Use | Tree | Deprecated | Index | Help
| Eclipse JDT Release 3.0
PREV NEXT | FRAMES NO FRAMES

## Deprecated API

Deprecated Classes
org.eclipse.jdt.launching.sourcelookup.ArchiveSourceLocation In 3.0, the debug platform provides source lookup facilities that should be used in place of the Java source lookup support provided in 2.0. The new facilities provide a source lookup director that coordinates source lookup among a set of participants, searching a set of source containers. See the following packages: `org.eclipse.debug.core.sourcelookup` and `org.eclipse.debug.core.sourcelookup.containers`. This class has been replaced by the following classes: `org.eclipse.debug.core.sourcelookup.containers.ArchiveSourceContainer` and `org.eclipse.debug.core.sourcelookup.containers.ExternalArchiveSourceContainer`.
org.eclipse.jdt.launching.sourcelookup.DirectorySourceLocation In 3.0, the debug platform provides source lookup facilities that should be used in place of the Java source lookup support provided in 2.0. The new facilities provide a source lookup director that coordinates source lookup among a set of participants, searching a set of source containers. See the following packages: `org.eclipse.debug.core.sourcelookup` and `org.eclipse.debug.core.sourcelookup.containers`. This class has been replaced by `org.eclipse.debug.core.sourcelookup.containers.DirectorySourceContainer`.
org.eclipse.jdt.core.jdom.DOMFactory The JDOM was made obsolete by the addition in 2.0 of the more powerful, fine-grained DOM/AST API found in the org.eclipse.jdt.core.dom package.
org.eclipse.jdt.ui.JavaElementContentProvider use the StandardJavaElementContentProvider instead
org.eclipse.jdt.launching.sourcelookup.JavaProjectSourceLocation In 3.0, the debug platform provides source lookup facilities that should be used in place of the Java source lookup support provided in 2.0. The new facilities provide a source lookup director that coordinates source lookup among a set of participants, searching a set of source containers. See the following packages: `org.eclipse.debug.core.sourcelookup` and `org.eclipse.debug.core.sourcelookup.containers`. This class has been replaced by `org.eclipse.jdt.launching.sourcelookup.containers.JavaProjectSourceContainer`.
org.eclipse.jdt.launching.sourcelookup.JavaSourceLocator In 3.0, the debug platform provides source lookup facilities that should be used in place of the Java source lookup support provided in 2.0. The new facilities provide a source lookup director that coordinates source lookup among a set of participants, searching a set of source containers. See the following packages: `org.eclipse.debug.core.sourcelookup` and `org.eclipse.debug.core.sourcelookup.containers`. This class has been replaced by a Java source lookup director and Java source lookup participant. To migrate to the new source lookup support clients should add two new attributes to their launch configuration type extensions: sourceLocatorId="org.eclipse.jdt.launching.sourceLocator.JavaSourceLookupDirector" sourcePathComputerId="org.eclipse.jdt.launching.sourceLookup.javaSourcePathComputer" The source locator id attribute specifies to use the Java source lookup director for launch configurations of the associated type, and the source path computer id attribute specifies the class to use when computing a default source lookup path for a launch configuration. The path computer referenced/provided (by the above id), computes a default source lookup path based on the support provided in the 2.0 release - i.e. a configuration's `ATTR_SOURCE_PATH_PROVIDER` attribute (if present), or a default source lookup path based on a configuration's runtime classpath. This class has been replaced by the Java source lookup director which is an internal class, but can be used via the `sourceLocatorId` attribute on a launch configuration type extension.
org.eclipse.jdt.debug.ui.JavaSourceLookupDialog In 3.0, the debug platform provides source lookup facilities that should be used in place of the Java source lookup support provided in 2.0. The new facilities provide a source lookup director that coordinates source lookup among a set of participants, searching a set of source containers. See the following packages: `org.eclipse.debug.core.sourcelookup` and `org.eclipse.debug.core.sourcelookup.containers`. This class has been replaced by a dialog in the debug platform - `org.eclipse.debug.ui.sourcelookup.SourceLookupDialog`.
org.eclipse.jdt.debug.ui.launchConfigurations.JavaSourceLookupTab In 3.0, the debug platform provides source lookup facilities that should be used in place of the Java source lookup support provided in 2.0. The new facilities provide a source lookup director that coordinates source lookup among a set of participants, searching a set of source containers. See the following packages: `org.eclipse.debug.core.sourcelookup` and `org.eclipse.debug.core.sourcelookup.containers`. This class has been replaced by a source lookup tab in the debug platform - `org.eclipse.debug.ui.sourcelookup.SourceLookupTab`.
org.eclipse.jdt.debug.ui.JavaUISourceLocator In 3.0, the debug platform provides source lookup facilities that should be used in place of the Java source lookup support provided in 2.0. The new facilities provide a source lookup director that coordinates source lookup among a set of participants, searching a set of source containers. See the following packages: `org.eclipse.debug.core.sourcelookup` and `org.eclipse.debug.core.sourcelookup.containers`. This class has been replaced by a Java source lookup director and Java source lookup participant. To migrate to the new source lookup support clients should add two new attributes to their launch configuration type extensions: sourceLocatorId="org.eclipse.jdt.launching.sourceLocator.JavaSourceLookupDirector" sourcePathComputerId="org.eclipse.jdt.launching.sourceLookup.javaSourcePathComputer" The source locator id attribute specifies to use the Java source lookup director for launch configurations of the associated type, and the source path computer id attribute specifies the class to use when computing a default source lookup path for a launch configuration. The path computer referenced/provided (by the above id), computes a default source lookup path based on the support provided in the 2.0 release - i.e. a configuration's `ATTR_SOURCE_PATH_PROVIDER` attribute (if present), or a default source lookup path based on a configuration's runtime classpath. This class has been replaced by the Java source lookup director which is an internal class, but can be used via the `sourceLocatorId` attribute on a launch configuration type extension.
org.eclipse.jdt.launching.sourcelookup.LocalFileStorage In 3.0 this class is now provided by the debug platform. Clients should use the replacement class `org.eclipse.debug.core.sourcelookup.containers.LocalFileStorage`
org.eclipse.jdt.launching.sourcelookup.PackageFragmentRootSourceLocation In 3.0, the debug platform provides source lookup facilities that should be used in place of the Java source lookup support provided in 2.0. The new facilities provide a source lookup director that coordinates source lookup among a set of participants, searching a set of source containers. See the following packages: `org.eclipse.debug.core.sourcelookup` and `org.eclipse.debug.core.sourcelookup.containers`. This class has been replaced by `org.eclipse.jdt.launching.sourcelookup.containers.PackageFragmentRootSourceContainer`.
org.eclipse.jdt.launching.sourcelookup.ZipEntryStorage In 3.0 this class is provided by the debug platform and clients should use the replacement class `org.eclipse.debug.core.sourcelookup.containers.ZipEntryStorage`.

Deprecated Interfaces
org.eclipse.jdt.core.IBufferFactory Use `WorkingCopyOwner` instead
org.eclipse.jdt.core.util.IClassFileDisassembler - should use ClassFileBytesDisassembler instead
org.eclipse.jdt.core.ICodeCompletionRequestor Use `CompletionRequestor` instead.
org.eclipse.jdt.core.ICodeFormatter - should use org.eclipse.jdt.core.formatter.CodeFormatter instead (note: options have changed)
org.eclipse.jdt.core.jdom.IDOMCompilationUnit The JDOM was made obsolete by the addition in 2.0 of the more powerful, fine-grained DOM/AST API found in the org.eclipse.jdt.core.dom package.
org.eclipse.jdt.core.jdom.IDOMFactory The JDOM was made obsolete by the addition in 2.0 of the more powerful, fine-grained DOM/AST API found in the org.eclipse.jdt.core.dom package.
org.eclipse.jdt.core.jdom.IDOMField The JDOM was made obsolete by the addition in 2.0 of the more powerful, fine-grained DOM/AST API found in the org.eclipse.jdt.core.dom package.
org.eclipse.jdt.core.jdom.IDOMImport The JDOM was made obsolete by the addition in 2.0 of the more powerful, fine-grained DOM/AST API found in the org.eclipse.jdt.core.dom package.
org.eclipse.jdt.core.jdom.IDOMInitializer The JDOM was made obsolete by the addition in 2.0 of the more powerful, fine-grained DOM/AST API found in the org.eclipse.jdt.core.dom package.
org.eclipse.jdt.core.jdom.IDOMMember The JDOM was made obsolete by the addition in 2.0 of the more powerful, fine-grained DOM/AST API found in the org.eclipse.jdt.core.dom package.
org.eclipse.jdt.core.jdom.IDOMMethod The JDOM was made obsolete by the addition in 2.0 of the more powerful, fine-grained DOM/AST API found in the org.eclipse.jdt.core.dom package.
org.eclipse.jdt.core.jdom.IDOMNode The JDOM was made obsolete by the addition in 2.0 of the more powerful, fine-grained DOM/AST API found in the org.eclipse.jdt.core.dom package.
org.eclipse.jdt.core.jdom.IDOMPackage The JDOM was made obsolete by the addition in 2.0 of the more powerful, fine-grained DOM/AST API found in the org.eclipse.jdt.core.dom package.
org.eclipse.jdt.core.jdom.IDOMType The JDOM was made obsolete by the addition in 2.0 of the more powerful, fine-grained DOM/AST API found in the org.eclipse.jdt.core.dom package.
org.eclipse.jdt.debug.core.IJavaPatternBreakpoint use `IJavaStratumLineBreakpoint` instead
org.eclipse.jdt.core.search.IJavaSearchResultCollector Since 3.0, the class `SearchRequestor` replaces this interface.
org.eclipse.jdt.launching.sourcelookup.IJavaSourceLocation In 3.0, the debug platform provides source lookup facilities that should be used in place of the Java source lookup support provided in 2.0. The new facilities provide a source lookup director that coordinates source lookup among a set of participants, searching a set of source containers. See the following packages: `org.eclipse.debug.core.sourcelookup` and `org.eclipse.debug.core.sourcelookup.containers`. This interface has been replaced by `org.eclipse.debug.core.sourcelookup.ISourceContainer`.
org.eclipse.jdt.launching.IRuntimeContainerComparator support has been added to `ClasspathContainerInitializer` to handle comparison of classpath containers. Use `ClasspathContainerInitializer.getComparisonID(IPath,IJavaProject)`. When a classpath container implements this interface, this interface is used to determine equality before using the support defined in `ClasspathContainerInitializer`.
org.eclipse.jdt.core.search.ISearchPattern Since 3.0, the class `SearchPattern` replaces this interface.
org.eclipse.jdt.core.IWorkingCopy Use `ICompilationUnit`instead

Deprecated Exceptions
org.eclipse.jdt.core.jdom.DOMException The JDOM was made obsolete by the addition in 2.0 of the more powerful, fine-grained DOM/AST API found in the org.eclipse.jdt.core.dom package.

Deprecated Fields
org.eclipse.jdt.ui.PreferenceConstants.APPEARANCE_OVERRIDE_INDICATOR Override Indicator is now controlled on the platform's decorator preference page
org.eclipse.jdt.launching.JavaRuntime.ATTR_CMDLINE - use `IProcess.ATTR_CMDLINE`
org.eclipse.jdt.ui.JavaUI.ATTR_CMDLINE
org.eclipse.jdt.core.search.IJavaSearchConstants.CASE_INSENSITIVE Use the methods that take the matchMode without `SearchPattern.R_CASE_SENSITIVE` as a matchRule instead.
org.eclipse.jdt.core.search.IJavaSearchConstants.CASE_SENSITIVE Use the methods that take the matchMode with `SearchPattern.R_CASE_SENSITIVE` as a matchRule instead.
org.eclipse.jdt.ui.PreferenceConstants.CODEGEN__FILE_COMMENTS New code template story: user can specify the new file code template.
org.eclipse.jdt.ui.PreferenceConstants.CODEGEN__JAVADOC_STUBS Use CODEGEN_ADD_COMMENTS instead (Name is more precise).
org.eclipse.jdt.ui.PreferenceConstants.CODEGEN__NON_JAVADOC_COMMENTS New code template story: user can specify the overriding method comment.
org.eclipse.jdt.ui.PreferenceConstants.CODEGEN_GETTERSETTER_PREFIX Use JavaCore preference store (key JavaCore. CODEASSIST_FIELD_PREFIXES and CODEASSIST_STATIC_FIELD_PREFIXES)
org.eclipse.jdt.ui.PreferenceConstants.CODEGEN_GETTERSETTER_SUFFIX Use setting from JavaCore preference store (key JavaCore. CODEASSIST_FIELD_SUFFIXES and CODEASSIST_STATIC_FIELD_SUFFIXES)
org.eclipse.jdt.ui.PreferenceConstants.CODEGEN_USE_GETTERSETTER_PREFIX Use JavaCore preference store (key JavaCore. CODEASSIST_FIELD_PREFIXES and CODEASSIST_STATIC_FIELD_PREFIXES)
org.eclipse.jdt.ui.PreferenceConstants.CODEGEN_USE_GETTERSETTER_SUFFIX Use JavaCore preference store (key JavaCore. CODEASSIST_FIELD_PREFIXES and CODEASSIST_STATIC_FIELD_PREFIXES)
org.eclipse.jdt.core.JavaCore.COMPILER_PB_INVALID_IMPORT - discontinued since turning off would violate language specs
org.eclipse.jdt.core.JavaCore.COMPILER_PB_UNREACHABLE_CODE - discontinued since turning off would violate language specs
org.eclipse.jdt.core.JavaCore.DEFAULT_TASK_PRIORITY - should use #DEFAULT_TASK_PRIORITIES instead
org.eclipse.jdt.core.JavaCore.DEFAULT_TASK_TAG - should use #DEFAULT_TASK_TAGS instead
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_ALT_SHIFT_HOVER As of 3.0, replaced by `PreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_BOOKMARK_INDICATION as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_BOOKMARK_INDICATION_COLOR as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_BOOKMARK_INDICATION_IN_OVERVIEW_RULER as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_CTRL_ALT_HOVER As of 3.0, replaced by `PreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_CTRL_ALT_SHIFT_HOVER As of 3.0, replaced by `PreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_CTRL_HOVER As of 3.0, replaced by `PreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_CTRL_SHIFT_HOVER As of 3.0, replaced by `PreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_CURRENT_LINE as of 3.0 replaced by `AbstractDecoratedTextEditorPreferenceConstants`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_CURRENT_LINE_COLOR as of 3.0 replaced by `AbstractDecoratedTextEditorPreferenceConstants`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_DEFAULT_HOVER As of 3.0, replaced by `PreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_DEFAULT_HOVER_CONFIGURED_ID As of 3.0, replaced by `PreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_ERROR_INDICATION_IN_OVERVIEW_RULER as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_LINE_NUMBER_RULER as of 3.0 replaced by `AbstractDecoratedTextEditorPreferenceConstants`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_LINE_NUMBER_RULER_COLOR as of 3.0 replaced by `AbstractDecoratedTextEditorPreferenceConstants`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_LINKED_POSITION_COLOR not used any longer as the linked positions are displayed as annotations
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_NO_HOVER_CONFIGURED_ID As of 3.0, replaced by `PreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_NONE_HOVER As of 3.0, replaced by `PreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_OVERVIEW_RULER as of 3.0 replaced by `AbstractDecoratedTextEditorPreferenceConstants`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_PRINT_MARGIN as of 3.0 replaced by `AbstractDecoratedTextEditorPreferenceConstants`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_PRINT_MARGIN_COLOR as of 3.0 replaced by `AbstractDecoratedTextEditorPreferenceConstants`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_PRINT_MARGIN_COLUMN as of 3.0 replaced by `AbstractDecoratedTextEditorPreferenceConstants`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_PROBLEM_INDICATION as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_PROBLEM_INDICATION_COLOR as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_SEARCH_RESULT_INDICATION as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_SEARCH_RESULT_INDICATION_COLOR as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_SEARCH_RESULT_INDICATION_IN_OVERVIEW_RULER as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_SHIFT_HOVER As of 3.0, replaced by `PreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_TAB_WIDTH As of 3.0 replaced by `AbstractDecoratedTextEditorPreferenceConstants.EDITOR_TAB_WIDTH`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_TASK_INDICATION as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_TASK_INDICATION_COLOR as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_TASK_INDICATION_IN_OVERVIEW_RULER as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_UNKNOWN_INDICATION as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_UNKNOWN_INDICATION_COLOR
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_UNKNOWN_INDICATION_IN_OVERVIEW_RULER as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_WARNING_INDICATION as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_WARNING_INDICATION_COLOR as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_WARNING_INDICATION_IN_OVERVIEW_RULER as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.core.search.IJavaSearchResultCollector.EXACT_MATCH Use `SearchMatch.A_ACCURATE` instead.
org.eclipse.jdt.core.search.IJavaSearchConstants.EXACT_MATCH Use `SearchPattern.R_EXACT_MATCH` instead.
org.eclipse.jdt.core.IJavaElementDelta.F_CLASSPATH_REORDER Use F_REORDER instead.
org.eclipse.jdt.core.JavaCore.FORMATTER_CLEAR_BLANK_LINES Use DefaultCodeFormatterConstants.FORMATTER_NUMBER_OF_EMPTY_LINES_TO_PRESERVE instead
org.eclipse.jdt.core.JavaCore.FORMATTER_COMPACT_ASSIGNMENT Use DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_BEFORE_ASSIGNMENT_OPERATOR instead
org.eclipse.jdt.core.JavaCore.FORMATTER_LINE_SPLIT Use DefaultCodeFormatterConstants.FORMATTER_LINE_SPLIT instead
org.eclipse.jdt.core.JavaCore.FORMATTER_NEWLINE_CONTROL Use DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_IN_CONTROL_STATEMENTS instead.
org.eclipse.jdt.core.JavaCore.FORMATTER_NEWLINE_ELSE_IF Use DefaultCodeFormatterConstants.FORMATTER_COMPACT_ELSE_IF instead
org.eclipse.jdt.core.JavaCore.FORMATTER_NEWLINE_EMPTY_BLOCK Use DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_IN_EMPTY_BLOCK instead
org.eclipse.jdt.core.JavaCore.FORMATTER_NEWLINE_OPENING_BRACE Use DefaultCodeFormatterConstants.FORMATTER_BRACE_POSITION_FOR_ANONYMOUS_TYPE_DECLARATION, DefaultCodeFormatterConstants.FORMATTER_BRACE_POSITION_FOR_BLOCK, DefaultCodeFormatterConstants.FORMATTER_BRACE_POSITION_FOR_CONSTRUCTOR_DECLARATION, DefaultCodeFormatterConstants.FORMATTER_BRACE_POSITION_FOR_METHOD_DECLARATION, DefaultCodeFormatterConstants.FORMATTER_BRACE_POSITION_FOR_SWITCH, DefaultCodeFormatterConstants.FORMATTER_BRACE_POSITION_FOR_TYPE_DECLARATION instead
org.eclipse.jdt.core.JavaCore.FORMATTER_SPACE_CASTEXPRESSION Use DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_AFTER_CLOSING_PAREN_IN_CAST instead
org.eclipse.jdt.core.JavaCore.FORMATTER_TAB_CHAR Use DefaultCodeFormatterConstants.FORMATTER_TAB_CHAR instead
org.eclipse.jdt.core.JavaCore.FORMATTER_TAB_SIZE Use DefaultCodeFormatterConstants.FORMATTER_TAB_SIZE instead
org.eclipse.jdt.ui.PreferenceConstants.ID_PROBLEM_HOVER as of 3.0, this hover is no longer available
org.eclipse.jdt.ui.actions.IJavaEditorActionDefinitionIds.INLINE_LOCAL_VARIABLE Use INLINE
org.eclipse.jdt.ui.actions.JdtActionConstants.INLINE_TEMP Use INLINE
org.eclipse.jdt.ui.text.IJavaColorConstants.JAVA_TYPE no longer used, replaced by `JAVA_KEYWORD`
org.eclipse.jdt.core.search.IJavaSearchConstants.PATTERN_MATCH Use `SearchPattern.R_PATTERN_MATCH` instead.
org.eclipse.jdt.core.search.IJavaSearchResultCollector.POTENTIAL_MATCH Use `SearchMatch.A_INACCURATE` instead.
org.eclipse.jdt.core.ElementChangedEvent.PRE_AUTO_BUILD - no longer used, such deltas are now notified during POST_CHANGE
org.eclipse.jdt.ui.text.JavaSourceViewerConfiguration.PREFERENCE_TAB_WIDTH As of 3.0, replaced by `AbstractDecoratedTextEditorPreferenceConstants.EDITOR_TAB_WIDTH`
org.eclipse.jdt.core.search.IJavaSearchConstants.PREFIX_MATCH Use `SearchPattern.R_PREFIX_MATCH` instead.
org.eclipse.jdt.ui.PreferenceConstants.REFACTOR_ERROR_PAGE_SEVERITY_THRESHOLD Use method `RefactoringCore.getConditionCheckingFailedSeverity()`.
org.eclipse.jdt.ui.PreferenceConstants.REFACTOR_ERROR_SEVERITY Use constant `RefactoringStatus.ERROR`
org.eclipse.jdt.ui.PreferenceConstants.REFACTOR_FATAL_SEVERITY Use constant `RefactoringStatus.FATAL`
org.eclipse.jdt.ui.PreferenceConstants.REFACTOR_INFO_SEVERITY Use constant `RefactoringStatus.INFO`
org.eclipse.jdt.ui.PreferenceConstants.REFACTOR_OK_SEVERITY Use constant `RefactoringStatus.OK`
org.eclipse.jdt.ui.PreferenceConstants.REFACTOR_WARNING_SEVERITY Use constant `RefactoringStatus.WARNING`
org.eclipse.jdt.ui.JavaElementLabelProvider.SHOW_CONTAINER Use SHOW_QUALIFIED or SHOW_ROOT instead
org.eclipse.jdt.ui.JavaElementLabelProvider.SHOW_CONTAINER_QUALIFICATION Use SHOW_QUALIFIED instead
org.eclipse.jdt.ui.actions.IJavaEditorActionDefinitionIds.SHOW_NEXT_PROBLEM as of 3.0 replaced by `ITextEditorActionDefinitionIds.GOTO_NEXT_ANNOTATION`
org.eclipse.jdt.ui.JavaElementLabelProvider.SHOW_POSTIFIX_QUALIFICATION SHOW_POST_QUALIFIED instead
org.eclipse.jdt.ui.actions.IJavaEditorActionDefinitionIds.SHOW_PREVIOUS_PROBLEM as of 3.0 replaced by `ITextEditorActionDefinitionIds.GOTO_PREVIOUS_ANNOTATION`
org.eclipse.jdt.ui.actions.IJavaEditorActionDefinitionIds.TOGGLE_PRESENTATION as of 3.0 replaced by `ITextEditorActionDefinitionIds.TOGGLE_SHOW_SELECTED_ELEMENT_ONLY`
org.eclipse.jdt.ui.PreferenceConstants.UPDATE_JAVA_VIEWS Since 3.0, views now always update while editing
org.eclipse.jdt.ui.refactoring.RenameSupport.UPDATE_JAVADOC_COMMENTS use UPDATE_REFERENCES or UPDATE_TEXTUAL_MATCHES or both.
org.eclipse.jdt.ui.PreferenceConstants.UPDATE_ON_SAVE Since 3.0, views now always update while editing
org.eclipse.jdt.ui.refactoring.RenameSupport.UPDATE_REGULAR_COMMENTS use UPDATE_TEXTUAL_MATCHES
org.eclipse.jdt.ui.refactoring.RenameSupport.UPDATE_STRING_LITERALS use UPDATE_TEXTUAL_MATCHES
org.eclipse.jdt.ui.PreferenceConstants.UPDATE_WHILE_EDITING Since 3.0, views now always update while editing

Deprecated Methods
org.eclipse.jdt.core.search.IJavaSearchResultCollector.aboutToStart() Replaced by `SearchRequestor.beginReporting()`.
org.eclipse.jdt.core.search.IJavaSearchResultCollector.accept(IResource, int, int, IJavaElement, int) Replaced by `SearchRequestor.acceptSearchMatch(SearchMatch)`.
org.eclipse.jdt.ui.text.JavaTextTools.adaptToPreferenceChange(PropertyChangeEvent) As of 3.0, no replacement
org.eclipse.jdt.ui.text.JavaTextTools.affectsBehavior(PropertyChangeEvent) As of 3.0, replaced by `JavaSourceViewerConfiguration.affectsTextPresentation(PropertyChangeEvent)`
org.eclipse.jdt.core.ICodeAssist.codeComplete(int, ICodeCompletionRequestor) Use `ICodeAssist.codeComplete(int, ICompletionRequestor)` instead.
org.eclipse.jdt.core.eval.IEvaluationContext.codeComplete(String, int, ICodeCompletionRequestor) - use codeComplete(String, int, ICompletionRequestor) instead
org.eclipse.jdt.core.ToolFactory.createCodeFormatter() - should use #createCodeFormatter(Map) instead. Extension point is discontinued
org.eclipse.jdt.core.ToolFactory.createDefaultClassFileDisassembler() - should use factory method creating ClassFileBytesDisassembler instead
org.eclipse.jdt.core.ToolFactory.createDefaultCodeFormatter(Map) - use #createCodeFormatter(Map) instead
org.eclipse.jdt.ui.wizards.NewTypeWizardPage.createInheritedMethods(IType, boolean, boolean, IImportsStructure, IProgressMonitor) Use createInheritedMethods(IType,boolean,boolean,IImportsManager,IProgressMonitor)
org.eclipse.jdt.core.search.SearchEngine.createJavaSearchScope(IResource[]) Use `SearchEngine.createJavaSearchScope(IJavaElement[])` instead.
org.eclipse.jdt.core.search.SearchEngine.createOrSearchPattern(ISearchPattern, ISearchPattern) Use `SearchPattern.createOrPattern(SearchPattern, SearchPattern)` instead.
org.eclipse.jdt.debug.core.JDIDebugModel.createPatternBreakpoint(IResource, String, String, int, int, int, int, boolean, Map) use `createStratumBreakpoint` instead
org.eclipse.jdt.core.search.SearchEngine.createSearchPattern(IJavaElement, int) Use `SearchPattern.createPattern(IJavaElement, int)` instead.
org.eclipse.jdt.core.search.SearchEngine.createSearchPattern(String, int, int, boolean) Use `SearchPattern.createPattern(String, int, int, int)` instead.
org.eclipse.jdt.ui.wizards.NewTypeWizardPage.createTypeMembers(IType, IImportsStructure, IProgressMonitor) Overwrite createTypeMembers(IType, IImportsManager, IProgressMonitor) instead
org.eclipse.jdt.core.search.IJavaSearchResultCollector.done() Replaced by `SearchRequestor.endReporting()`.
org.eclipse.jdt.launching.SocketUtil.findUnusedLocalPort(String, int, int) Use `findFreePort()` instead. It is possible that this method can return a port that is already in use since the implementation does not bind to the given port to ensure that it is free.
org.eclipse.jdt.ui.JavaUI.getBufferFactory() `IBufferFactory` has been replaced by `WorkingCopyOwner`. The Java UI plug-in uses the primary working copy owner that can be accessed with `null` in API's that require an owner
org.eclipse.jdt.ui.text.JavaTextTools.getCodeScanner() As of 3.0, replaced by `JavaSourceViewerConfiguration.getCodeScanner()`
org.eclipse.jdt.core.dom.Javadoc.getComment() The comment string was replaced in the 3.0 release by a representation of the structure of the doc comment. See `tags`.
org.eclipse.jdt.debug.eval.IEvaluationResult.getErrors() use getErrorMessages()
org.eclipse.jdt.debug.eval.ICompiledExpression.getErrors() use getErrorMessages()
org.eclipse.jdt.ui.wizards.NewTypeWizardPage.getFileComment(ICompilationUnit) Instead of file templates, the new type code template specifies the stub for a compilation unit.
org.eclipse.jdt.debug.core.IJavaExceptionBreakpoint.getFilters() Use getExclusionFilters() or getInclusionFilters()
org.eclipse.jdt.ui.ITypeHierarchyViewPart.getInput() use getInputElement instead
org.eclipse.jdt.ui.text.JavaTextTools.getJavaDocScanner() As of 3.0, replaced by `JavaSourceViewerConfiguration.getJavaDocScanner()`
org.eclipse.jdt.core.dom.Statement.getLeadingComment() This feature was removed in the 2.1 release because it was only a partial, and inadequate, solution to the issue of associating comments with statements. Furthermore, AST.parseCompilationUnit did not associate leading comments, making this moot. Clients that need to access comments preceding a statement should either consult the compilation unit's comment table or use a scanner to reanalyze the source text immediately preceding the statement's source range.
org.eclipse.jdt.ui.text.JavaTextTools.getMultilineCommentScanner() As of 3.0, replaced by `JavaSourceViewerConfiguration.getMultilineCommentScanner()`
org.eclipse.jdt.core.IJavaProject.getPackageFragmentRoots(IClasspathEntry) Use IJavaProject#findPackageFragmentRoots instead
org.eclipse.jdt.ui.text.JavaTextTools.getPartitionManagingPositionCategories() As of 3.0, replaced by `TextUtilities.computePartitionManagingCategories(IDocument)`
org.eclipse.jdt.ui.text.JavaSourceViewerConfiguration.getPreferenceStore() As of 3.0
org.eclipse.jdt.ui.StandardJavaElementContentProvider.getProvideWorkingCopy() Since 3.0 compilation unit children are always provided as working copies. The Java model does not support the 'original' mode anymore.
org.eclipse.jdt.core.IClasspathEntry.getResolvedEntry() - use JavaCore.getResolvedClasspathEntry(...)
org.eclipse.jdt.ui.JavaUI.getSharedWorkingCopies() Use `JavaCore.getWorkingCopies(org.eclipse.jdt.core.WorkingCopyOwner)` instead with `null` as argument for owner.
org.eclipse.jdt.core.JavaCore.getSharedWorkingCopies(IBufferFactory) - should use #getWorkingCopies(WorkingCopyOwner) instead
org.eclipse.jdt.ui.JavaUI.getSharedWorkingCopiesOnClasspath() Use `JavaCore.getWorkingCopies(org.eclipse.jdt.core.WorkingCopyOwner)` instead and filter the list with `IJavaProject.isOnClasspath(IJavaElement)`.
org.eclipse.jdt.ui.text.JavaTextTools.getSinglelineCommentScanner() As of 3.0, replaced by `JavaSourceViewerConfiguration.getSinglelineCommentScanner()`
org.eclipse.jdt.core.dom.Message.getSourcePosition() Use getStartPosition() instead.
org.eclipse.jdt.core.IJavaModelStatus.getString() Use IStatus#getMessage instead
org.eclipse.jdt.ui.text.JavaTextTools.getStringScanner() As of 3.0, replaced by `JavaSourceViewerConfiguration.getStringScanner()`
org.eclipse.jdt.ui.wizards.NewTypeWizardPage.getTemplate(String, ICompilationUnit) Use getTemplate(String,ICompilationUnit,int)
org.eclipse.jdt.ui.wizards.NewTypeWizardPage.getTypeComment(ICompilationUnit) Use getTypeComment(ICompilationUnit, String)
org.eclipse.jdt.core.IClassFile.getWorkingCopy(IProgressMonitor, IBufferFactory) Use getWorkingCopy(WorkingCopyOwner, IProgressMonitor) instead
org.eclipse.jdt.core.search.IJavaSearchScope.includesBinaries() Use `SearchEngine.createJavaSearchScope(IJavaElement[])` with the package fragment roots that correspond to the binaries instead.
org.eclipse.jdt.core.search.IJavaSearchScope.includesClasspaths() Use `SearchEngine.createJavaSearchScope(IJavaElement[])` with a Java project instead.
org.eclipse.jdt.debug.core.IJavaExceptionBreakpoint.isInclusiveFiltered() Exception breakpoints can have a mixed set of filters and this method is maintained strictly for API backwards compatibility
org.eclipse.jdt.core.JavaConventions.isOverlappingRoots(IPath, IPath) Overlapping roots are allowed in 2.1
org.eclipse.jdt.ui.JavaElementSorter.isSorterProperty(Object, Object) Bug 22518. Method never used: does not override ViewerSorter#isSorterProperty(Object, String). Method could be removed, but kept for API compatibility.
org.eclipse.jdt.ui.jarpackager.JarPackageData.logErrors() will be removed in final 2.0
org.eclipse.jdt.ui.jarpackager.JarPackageData.logWarnings() will be removed in final 2.0
org.eclipse.jdt.core.IType.newSupertypeHierarchy(IWorkingCopy[], IProgressMonitor) use #newSupertypeHierarchy(ICompilationUnit[], IProgressMonitor) instead
org.eclipse.jdt.core.IType.newTypeHierarchy(IWorkingCopy[], IProgressMonitor) use #newTypeHierarchy(ICompilationUnit[], IProgressMonitor) instead
org.eclipse.jdt.core.dom.AST.parseCompilationUnit(char[]) Use `ASTParser` instead.
org.eclipse.jdt.core.dom.AST.parseCompilationUnit(char[], String, IJavaProject) Use `ASTParser` instead.
org.eclipse.jdt.core.dom.AST.parseCompilationUnit(IClassFile, boolean) Use `ASTParser` instead.
org.eclipse.jdt.core.dom.AST.parseCompilationUnit(ICompilationUnit, boolean) Use `ASTParser` instead.
org.eclipse.jdt.core.JavaCore.removeClasspathVariable(String) - use version with extra IProgressMonitor
org.eclipse.jdt.ui.JavaUI.revealInEditor(IEditorPart, ISourceReference) use `revealInEditor(IEditorPart, IJavaElement)` instead
org.eclipse.jdt.core.search.SearchEngine.search(IWorkspace, IJavaElement, int, IJavaSearchScope, IJavaSearchResultCollector) Use `SearchEngine.search(SearchPattern, SearchParticipant[], IJavaSearchScope, SearchRequestor, IProgressMonitor)` instead.
org.eclipse.jdt.core.search.SearchEngine.search(IWorkspace, ISearchPattern, IJavaSearchScope, IJavaSearchResultCollector) Use `SearchEngine.search(SearchPattern, SearchParticipant[], IJavaSearchScope, SearchRequestor, IProgressMonitor)` instead.
org.eclipse.jdt.core.search.SearchEngine.search(IWorkspace, String, int, int, IJavaSearchScope, IJavaSearchResultCollector) Use `SearchEngine.search(SearchPattern, SearchParticipant[], IJavaSearchScope, SearchRequestor, IProgressMonitor)` instead.
org.eclipse.jdt.core.search.SearchEngine.searchAllTypeNames(IWorkspace, char[], char[], int, boolean, int, IJavaSearchScope, ITypeNameRequestor, int, IProgressMonitor) Use `SearchEngine.searchAllTypeNames(char[], char[], int, int, IJavaSearchScope, ITypeNameRequestor, int, IProgressMonitor)` instead
org.eclipse.jdt.core.search.SearchEngine.searchDeclarationsOfAccessedFields(IWorkspace, IJavaElement, IJavaSearchResultCollector) Use `SearchEngine.searchDeclarationsOfAccessedFields(IJavaElement, SearchRequestor, IProgressMonitor)` instead.
org.eclipse.jdt.core.search.SearchEngine.searchDeclarationsOfReferencedTypes(IWorkspace, IJavaElement, IJavaSearchResultCollector) Use `SearchEngine.searchDeclarationsOfReferencedTypes(IJavaElement, SearchRequestor, IProgressMonitor)` instead.
org.eclipse.jdt.core.search.SearchEngine.searchDeclarationsOfSentMessages(IWorkspace, IJavaElement, IJavaSearchResultCollector) Use `SearchEngine.searchDeclarationsOfSentMessages(IJavaElement, SearchRequestor, IProgressMonitor)` instead.
org.eclipse.jdt.core.JavaCore.setClasspathVariable(String, IPath) - use API with IProgressMonitor
org.eclipse.jdt.core.dom.Javadoc.setComment(String) The comment string was replaced in the 3.0 release by a representation of the structure of the doc comment. See `tags`.
org.eclipse.jdt.debug.core.IJavaExceptionBreakpoint.setFilters(String[], boolean) Exception breakpoints can have a mixed set of filters. Use setInclusiveFilters(String[] filters) or setExclusiveFilters(String[] filters)
org.eclipse.jdt.core.search.IJavaSearchScope.setIncludesBinaries(boolean) Use `SearchEngine.createJavaSearchScope(IJavaElement[])` with the package fragment roots that correspond to the binaries instead.
org.eclipse.jdt.core.search.IJavaSearchScope.setIncludesClasspaths(boolean) Use `SearchEngine.createJavaSearchScope(IJavaElement[])` with a Java project instead.
org.eclipse.jdt.ui.ITypeHierarchyViewPart.setInput(IType) use setInputElement instead
org.eclipse.jdt.core.dom.Statement.setLeadingComment(String) This feature was removed in the 2.1 release because it was only a partial, and inadequate, solution to the issue of associating comments with statements.
org.eclipse.jdt.ui.jarpackager.JarPackageData.setLogErrors(boolean) will be removed in final 2.0
org.eclipse.jdt.ui.jarpackager.JarPackageData.setLogWarnings(boolean) will be removed in final 2.0
org.eclipse.jdt.ui.StandardJavaElementContentProvider.setProvideWorkingCopy(boolean) Since 3.0 compilation unit children are always provided from the working copy. The Java model offers a unified world and does not support the 'original' mode anymore.

Deprecated Constructors
org.eclipse.jdt.ui.text.JavaSourceViewerConfiguration(JavaTextTools, ITextEditor) As of 3.0, replaced by `JavaSourceViewerConfiguration.JavaSourceViewerConfiguration(IColorManager, IPreferenceStore, ITextEditor, String)`
org.eclipse.jdt.core.search.SearchEngine(IWorkingCopy[]) Use `SearchEngine.SearchEngine(ICompilationUnit[])` instead.
org.eclipse.jdt.ui.StandardJavaElementContentProvider(boolean, boolean) Use `StandardJavaElementContentProvider.StandardJavaElementContentProvider(boolean)` instead. Since 3.0 compilation unit children are always provided as working copies. The Java Model does not support the 'original' mode anymore.

Overview | Package | Class | Use | Tree | Deprecated | Index | Help
| Eclipse JDT Release 3.0
PREV NEXT | FRAMES NO FRAMES

Copyright (c) IBM Corp. and others 2000, 2004. All Rights Reserved.