# Deprecated API

## Contents

- Interfaces
- Classes
- Exceptions
- Fields
- Methods
- Constructors

Interfaces
org.eclipse.ant.ui.launching.IAntLaunchConfigurationConstants: use `IAntLaunchConstants`
org.eclipse.jdt.core.IBufferFactory: Use `WorkingCopyOwner` instead
org.eclipse.jdt.core.ICodeCompletionRequestor: Use `CompletionRequestor` instead.
org.eclipse.jdt.core.ICodeFormatter: Use `CodeFormatter` instead (note: options have changed)
org.eclipse.jdt.core.ICompletionRequestor: Use `CompletionRequestor` instead.
org.eclipse.jdt.core.IWorkingCopy: Use `ICompilationUnit` instead
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.core.search.IJavaSearchResultCollector: Since 3.0, the class `SearchRequestor` replaces this interface.
org.eclipse.jdt.core.search.ISearchPattern: Since 3.0, the class `SearchPattern` replaces this interface.
org.eclipse.jdt.core.search.ITypeNameRequestor: Use abstract class `TypeNameRequestor` instead.
org.eclipse.jdt.core.util.IClassFileDisassembler: Use `ClassFileBytesDisassembler` instead
org.eclipse.jdt.debug.core.IJavaPatternBreakpoint: use `IJavaStratumLineBreakpoint` instead
org.eclipse.jdt.junit.ITestRunListener: As of 3.3, replaced by `TestRunListener`
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.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.ui.text.java.IJavadocCompletionProcessor: As of 3.2, replaced by `org.eclipse.jdt.ui.javaCompletionProposalComputer` extension-point.

Classes
org.eclipse.jdt.core.CompletionRequestorAdapter: Subclass `CompletionRequestor` instead.
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.core.refactoring.descriptors.RenameLocalVariableDescriptor: since 1.2 merged into `RenameJavaElementDescriptor`
org.eclipse.jdt.core.refactoring.descriptors.RenameResourceDescriptor: since 1.2, use `RenameResourceDescriptor` from `org.eclipse.ltk.core.refactoring` instead.

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.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.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.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.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.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`.
org.eclipse.jdt.ui.actions.FindStringsToExternalizeAction: use `ExternalizeStringsAction` instead
org.eclipse.jdt.ui.actions.OpenExternalJavadocAction: As of 3.6, replaced by `OpenAttachedJavadocAction`
org.eclipse.jdt.ui.actions.ShowActionGroup: As of 3.5, got replaced by generic Navigate > Show In >
org.eclipse.jdt.ui.actions.ShowInNavigatorViewAction: As of 3.5, got replaced by generic Navigate > Show In >
org.eclipse.jdt.ui.actions.ShowInPackageViewAction: As of 3.5, got replaced by generic Navigate > Show In >
org.eclipse.jdt.ui.CodeGeneration: See `CodeGeneration`
org.eclipse.jdt.ui.jarpackager.JarWriter: use `JarWriter3` instead.
org.eclipse.jdt.ui.jarpackager.JarWriter2: Use `JarWriter3` instead which leverages new `EFS` support
org.eclipse.jdt.ui.JavaElementContentProvider: use the StandardJavaElementContentProvider instead
org.eclipse.jdt.ui.JavaElementSorter: use `JavaElementComparator` instead.
org.eclipse.jdt.ui.SharedASTProvider: Use `SharedASTProviderCore` instead.
org.eclipse.jdt.ui.wizards.NewJavaProjectWizardPage: Use `NewJavaProjectWizardPageTwo` or `JavaCapabilityConfigurationPage`.

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.

Fields
org.eclipse.ant.ui.launching.IAntLaunchConfigurationConstants.ATTR_ANT_AFTER_CLEAN_TARGETS: use `IAntLaunchConstants.ATTR_ANT_AFTER_CLEAN_TARGETS`
org.eclipse.ant.ui.launching.IAntLaunchConfigurationConstants.ATTR_ANT_AUTO_TARGETS: use `IAntLaunchConstants.ATTR_ANT_AUTO_TARGETS`
org.eclipse.ant.ui.launching.IAntLaunchConfigurationConstants.ATTR_ANT_CLEAN_TARGETS: use `IAntLaunchConstants.ATTR_ANT_CLEAN_TARGETS`
org.eclipse.ant.ui.launching.IAntLaunchConfigurationConstants.ATTR_ANT_MANUAL_TARGETS: use `IAntLaunchConstants.ATTR_ANT_MANUAL_TARGETS`
org.eclipse.ant.ui.launching.IAntLaunchConfigurationConstants.ATTR_ANT_PROPERTIES: use `IAntLaunchConstants.ATTR_ANT_PROPERTIES`
org.eclipse.ant.ui.launching.IAntLaunchConfigurationConstants.ATTR_ANT_PROPERTY_FILES: use `IAntLaunchConstants.ATTR_ANT_PROPERTY_FILES`
org.eclipse.ant.ui.launching.IAntLaunchConfigurationConstants.ATTR_ANT_TARGETS: use `IAntLaunchConstants.ATTR_ANT_TARGETS`
org.eclipse.ant.ui.launching.IAntLaunchConfigurationConstants.ATTR_DEFAULT_VM_INSTALL: use `IAntLaunchConstants.ATTR_DEFAULT_VM_INSTALL`
org.eclipse.ant.ui.launching.IAntLaunchConfigurationConstants.ATTR_HIDE_INTERNAL_TARGETS: use `IAntLaunchConstants.ATTR_HIDE_INTERNAL_TARGETS`
org.eclipse.ant.ui.launching.IAntLaunchConfigurationConstants.ATTR_SORT_TARGETS: use `IAntLaunchConstants.ATTR_SORT_TARGETS`
org.eclipse.ant.ui.launching.IAntLaunchConfigurationConstants.ATTR_TARGETS_UPDATED: use `IAntLaunchConstants.ATTR_TARGETS_UPDATED`
org.eclipse.ant.ui.launching.IAntLaunchConfigurationConstants.ID_ANT_BUILDER_LAUNCH_CONFIGURATION_TYPE: use `IAntLaunchConstants.ID_ANT_BUILDER_LAUNCH_CONFIGURATION_TYPE`
org.eclipse.ant.ui.launching.IAntLaunchConfigurationConstants.ID_ANT_LAUNCH_CONFIGURATION_TYPE: use `IAntLaunchConstants.ID_ANT_LAUNCH_CONFIGURATION_TYPE`
org.eclipse.ant.ui.launching.IAntLaunchConfigurationConstants.ID_ANT_PROCESS_TYPE: use `IAntLaunchConstants.ID_ANT_PROCESS_TYPE`
org.eclipse.jdt.core.compiler.IProblem.AnnotationFieldNeedConstantInitialization: - problem is no longer generated (code is legite)
org.eclipse.jdt.core.compiler.IProblem.ArgumentTypeAmbiguous: - problem is no longer generated, use `IProblem.AmbiguousType` instead
org.eclipse.jdt.core.compiler.IProblem.ArgumentTypeCannotBeVoidArray: - problem is no longer generated, use `IProblem.CannotAllocateVoidArray` instead
org.eclipse.jdt.core.compiler.IProblem.ArgumentTypeInheritedNameHidesEnclosingName: - problem is no longer generated, use `IProblem.InheritedTypeHidesEnclosingName` instead
org.eclipse.jdt.core.compiler.IProblem.ArgumentTypeInternalNameProvided: - problem is no longer generated, use `IProblem.InternalTypeNameProvided` instead
org.eclipse.jdt.core.compiler.IProblem.ArgumentTypeNotFound: - problem is no longer generated, use `IProblem.UndefinedType` instead
org.eclipse.jdt.core.compiler.IProblem.ArgumentTypeNotVisible: - problem is no longer generated, use `IProblem.NotVisibleType` instead
org.eclipse.jdt.core.compiler.IProblem.ExceptionTypeAmbiguous: - problem is no longer generated, use `IProblem.AmbiguousType` instead
org.eclipse.jdt.core.compiler.IProblem.ExceptionTypeInheritedNameHidesEnclosingName: - problem is no longer generated, use `IProblem.InheritedTypeHidesEnclosingName` instead
org.eclipse.jdt.core.compiler.IProblem.ExceptionTypeInternalNameProvided: - problem is no longer generated, use `IProblem.InternalTypeNameProvided` instead
org.eclipse.jdt.core.compiler.IProblem.ExceptionTypeNotFound: - problem is no longer generated, use `IProblem.UndefinedType` instead
org.eclipse.jdt.core.compiler.IProblem.ExceptionTypeNotVisible: - problem is no longer generated, use `IProblem.NotVisibleType` instead
org.eclipse.jdt.core.compiler.IProblem.FieldTypeAmbiguous: - problem is no longer generated, use `IProblem.AmbiguousType` instead
org.eclipse.jdt.core.compiler.IProblem.FieldTypeInheritedNameHidesEnclosingName: - problem is no longer generated, use `IProblem.InheritedTypeHidesEnclosingName` instead
org.eclipse.jdt.core.compiler.IProblem.FieldTypeInternalNameProvided: - problem is no longer generated, use `IProblem.InternalTypeNameProvided` instead
org.eclipse.jdt.core.compiler.IProblem.FieldTypeNotFound: - problem is no longer generated, use `IProblem.UndefinedType` instead
org.eclipse.jdt.core.compiler.IProblem.FieldTypeNotVisible: - problem is no longer generated, use `IProblem.NotVisibleType` instead
org.eclipse.jdt.core.compiler.IProblem.IllegalModifierForLocalEnum: - problem could not be reported, enums cannot be local takes precedence
org.eclipse.jdt.core.compiler.IProblem.ImportAmbiguous: - problem is no longer generated, use `IProblem.AmbiguousType` instead
org.eclipse.jdt.core.compiler.IProblem.ImportInheritedNameHidesEnclosingName: - problem is no longer generated, use `IProblem.InheritedTypeHidesEnclosingName` instead
org.eclipse.jdt.core.compiler.IProblem.ImportInternalNameProvided: - problem is no longer generated, use `IProblem.InternalTypeNameProvided` instead
org.eclipse.jdt.core.compiler.IProblem.ImportNotVisible: - problem is no longer generated, use `IProblem.NotVisibleType` instead
org.eclipse.jdt.core.compiler.IProblem.InterfaceAmbiguous: - problem is no longer generated, use `IProblem.AmbiguousType` instead
org.eclipse.jdt.core.compiler.IProblem.InterfaceInheritedNameHidesEnclosingName: - problem is no longer generated, use `IProblem.InheritedTypeHidesEnclosingName` instead
org.eclipse.jdt.core.compiler.IProblem.InterfaceInternalNameProvided: - problem is no longer generated, use `IProblem.InternalTypeNameProvided` instead
org.eclipse.jdt.core.compiler.IProblem.InterfaceNotFound: - problem is no longer generated, use `IProblem.UndefinedType` instead
org.eclipse.jdt.core.compiler.IProblem.InterfaceNotVisible: - problem is no longer generated, use `IProblem.NotVisibleType` instead
org.eclipse.jdt.core.compiler.IProblem.InvalidTypeExpression: - problem is no longer generated
org.eclipse.jdt.core.compiler.IProblem.LambdaShapeComputationError: - problem is no longer generated (implementation issue has been resolved)
org.eclipse.jdt.core.compiler.IProblem.LocalVariableCannotBeNull: - problem is no longer generated, use `IProblem.RedundantNullCheckOnNonNullLocalVariable` instead
org.eclipse.jdt.core.compiler.IProblem.LocalVariableCanOnlyBeNull: - problem is no longer generated, use `IProblem.NullLocalVariableReference`, `IProblem.RedundantNullCheckOnNullLocalVariable` or `IProblem.RedundantLocalVariableNullAssignment` instead
org.eclipse.jdt.core.compiler.IProblem.LocalVariableMayBeNull: - problem is no longer generated, use `IProblem.PotentialNullLocalVariableReference` instead
org.eclipse.jdt.core.compiler.IProblem.MultipleFunctionalInterfaces: This problem is no longer reported; number Of functional interface is not an issue, number of abstract methods is.
org.eclipse.jdt.core.compiler.IProblem.MustSpecifyPackage: - problem is no longer generated
org.eclipse.jdt.core.compiler.IProblem.ReturnTypeAmbiguous: - problem is no longer generated, use `IProblem.AmbiguousType` instead
org.eclipse.jdt.core.compiler.IProblem.ReturnTypeCannotBeVoidArray: - problem is no longer generated, use `IProblem.CannotAllocateVoidArray` instead
org.eclipse.jdt.core.compiler.IProblem.ReturnTypeInheritedNameHidesEnclosingName: - problem is no longer generated, use `IProblem.InheritedTypeHidesEnclosingName` instead
org.eclipse.jdt.core.compiler.IProblem.ReturnTypeInternalNameProvided: - problem is no longer generated, use `IProblem.InternalTypeNameProvided` instead
org.eclipse.jdt.core.compiler.IProblem.ReturnTypeNotFound: - problem is no longer generated, use `IProblem.UndefinedType` instead
org.eclipse.jdt.core.compiler.IProblem.ReturnTypeNotVisible: - problem is no longer generated, use `IProblem.NotVisibleType` instead
org.eclipse.jdt.core.compiler.IProblem.SuperclassAmbiguous: - problem is no longer generated, use `IProblem.AmbiguousType` instead
org.eclipse.jdt.core.compiler.IProblem.SuperclassInheritedNameHidesEnclosingName: - problem is no longer generated, use `IProblem.InheritedTypeHidesEnclosingName` instead
org.eclipse.jdt.core.compiler.IProblem.SuperclassInternalNameProvided: - problem is no longer generated, use `IProblem.InternalTypeNameProvided` instead
org.eclipse.jdt.core.compiler.IProblem.SuperclassNotFound: - problem is no longer generated, use `IProblem.UndefinedType` instead
org.eclipse.jdt.core.compiler.IProblem.SuperclassNotVisible: - problem is no longer generated, use `IProblem.NotVisibleType` instead
org.eclipse.jdt.core.compiler.IProblem.UnnecessaryArgumentCast: - no longer generated, use `IProblem.UnnecessaryCast` instead
org.eclipse.jdt.core.compiler.IProblem.VariableTypeCannotBeVoidArray: - problem is no longer generated, use `IProblem.CannotAllocateVoidArray` instead

org.eclipse.jdt.core.compiler.ITerminalSymbols.TokenNameIdentifier

With the introduction of "restricted keywords" in Java 9, classification of tokens by a scanner is inherently unreliable. Any token classified as an identifier could still be a "restricted keyword". Future versions of Java will introduce more words that have special syntactical meaning in specific contexts. For reliably detecting an identifier the only real solution is to use a parser instead (see also the caveat at the top of the interface documentation of `IScanner`).

org.eclipse.jdt.core.dom.ArrayType.COMPONENT_TYPE_PROPERTY: In the JLS8 API, this property is replaced by `ArrayType.ELEMENT_TYPE_PROPERTY` and `ArrayType.DIMENSIONS_PROPERTY`.
org.eclipse.jdt.core.dom.AST.JLS10: Clients should use the `AST.JLS11` AST API instead.
org.eclipse.jdt.core.dom.AST.JLS2: Clients should use the `AST.JLS11` AST API instead.
org.eclipse.jdt.core.dom.AST.JLS3: Clients should use the `AST.JLS11` AST API instead.
org.eclipse.jdt.core.dom.AST.JLS4: Clients should use the `AST.JLS11` AST API instead.
org.eclipse.jdt.core.dom.AST.JLS8: Clients should use the `AST.JLS11` AST API instead.
org.eclipse.jdt.core.dom.AST.JLS9: Clients should use the `AST.JLS11` AST API instead.
org.eclipse.jdt.core.dom.ClassInstanceCreation.NAME_PROPERTY: In the JLS3 API, this property is replaced by `ClassInstanceCreation.TYPE_PROPERTY`.
org.eclipse.jdt.core.dom.FieldDeclaration.MODIFIERS_PROPERTY: In the JLS3 API, this property is replaced by `FieldDeclaration.MODIFIERS2_PROPERTY`.
org.eclipse.jdt.core.dom.Initializer.MODIFIERS_PROPERTY: In the JLS3 API, this property is replaced by `Initializer.MODIFIERS2_PROPERTY`.
org.eclipse.jdt.core.dom.Javadoc.COMMENT_PROPERTY: Replaced by `Javadoc.TAGS_PROPERTY` in the JLS3 API.
org.eclipse.jdt.core.dom.MethodDeclaration.EXTRA_DIMENSIONS_PROPERTY: In JLS8 and later, use `MethodDeclaration.EXTRA_DIMENSIONS2_PROPERTY` instead.
org.eclipse.jdt.core.dom.MethodDeclaration.MODIFIERS_PROPERTY: In the JLS3 API, this property is replaced by `MethodDeclaration.MODIFIERS2_PROPERTY`.
org.eclipse.jdt.core.dom.MethodDeclaration.RETURN_TYPE_PROPERTY: In the JLS3 API, this property is replaced by `MethodDeclaration.RETURN_TYPE2_PROPERTY`.
org.eclipse.jdt.core.dom.MethodDeclaration.THROWN_EXCEPTIONS_PROPERTY: In JLS8 and later, use `MethodDeclaration.THROWN_EXCEPTION_TYPES_PROPERTY` instead.
org.eclipse.jdt.core.dom.SingleVariableDeclaration.EXTRA_DIMENSIONS_PROPERTY: In JLS8 and later, use `SingleVariableDeclaration.EXTRA_DIMENSIONS2_PROPERTY` instead.
org.eclipse.jdt.core.dom.SingleVariableDeclaration.MODIFIERS_PROPERTY: In the JLS3 API, this property is replaced by `SingleVariableDeclaration.MODIFIERS2_PROPERTY`.
org.eclipse.jdt.core.dom.TryStatement.RESOURCES_PROPERTY: In the JLS9 API, this property is replaced by `TryStatement.RESOURCES2_PROPERTY`.
org.eclipse.jdt.core.dom.TypeDeclaration.MODIFIERS_PROPERTY: In the JLS3 API, this property is replaced by `TypeDeclaration.MODIFIERS2_PROPERTY`.
org.eclipse.jdt.core.dom.TypeDeclaration.SUPER_INTERFACES_PROPERTY: In the JLS3 API, this property is replaced by `TypeDeclaration.SUPER_INTERFACE_TYPES_PROPERTY`.
org.eclipse.jdt.core.dom.TypeDeclaration.SUPERCLASS_PROPERTY: In the JLS3 API, this property is replaced by `TypeDeclaration.SUPERCLASS_TYPE_PROPERTY`.
org.eclipse.jdt.core.dom.TypeDeclarationStatement.TYPE_DECLARATION_PROPERTY: In the JLS3 API, this property is replaced by `TypeDeclarationStatement.DECLARATION_PROPERTY`.
org.eclipse.jdt.core.dom.VariableDeclarationExpression.MODIFIERS_PROPERTY: In the JLS3 API, this property is replaced by `VariableDeclarationExpression.MODIFIERS2_PROPERTY`.
org.eclipse.jdt.core.dom.VariableDeclarationFragment.EXTRA_DIMENSIONS_PROPERTY: in JLS8 and later, use `VariableDeclarationFragment.EXTRA_DIMENSIONS2_PROPERTY` instead.
org.eclipse.jdt.core.dom.VariableDeclarationStatement.MODIFIERS_PROPERTY: In the JLS3 API, this property is replaced by `VariableDeclarationStatement.MODIFIERS2_PROPERTY`.
org.eclipse.jdt.core.ElementChangedEvent.PRE_AUTO_BUILD: - no longer used, such deltas are now notified during POST_CHANGE

org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants.FORMATTER_ALIGNMENT_FOR_BINARY_EXPRESSION

Use new settings instead: `DefaultCodeFormatterConstants.FORMATTER_ALIGNMENT_FOR_MULTIPLICATIVE_OPERATOR`, `DefaultCodeFormatterConstants.FORMATTER_ALIGNMENT_FOR_ADDITIVE_OPERATOR`, `DefaultCodeFormatterConstants.FORMATTER_ALIGNMENT_FOR_STRING_CONCATENATION`, `DefaultCodeFormatterConstants.FORMATTER_ALIGNMENT_FOR_BITWISE_OPERATOR`, `DefaultCodeFormatterConstants.FORMATTER_ALIGNMENT_FOR_LOGICAL_OPERATOR`

org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants.FORMATTER_COMMENT_CLEAR_BLANK_LINES: Use `DefaultCodeFormatterConstants.FORMATTER_COMMENT_CLEAR_BLANK_LINES_IN_BLOCK_COMMENT` and `DefaultCodeFormatterConstants.FORMATTER_COMMENT_CLEAR_BLANK_LINES_IN_JAVADOC_COMMENT`
org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants.FORMATTER_COMMENT_FORMAT: Use multiple settings for each kind of comments. See `DefaultCodeFormatterConstants.FORMATTER_COMMENT_FORMAT_BLOCK_COMMENT`, `DefaultCodeFormatterConstants.FORMATTER_COMMENT_FORMAT_JAVADOC_COMMENT` and `DefaultCodeFormatterConstants.FORMATTER_COMMENT_FORMAT_LINE_COMMENT`.

org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION

All new options must be enabled to activate old strategy `DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION_ON_MEMBER` `DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION_ON_LOCAL_VARIABLE` `DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION_ON_PARAMETER`

org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION_ON_MEMBER

All new options must be enabled to activate old strategy `DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION_ON_FIELD` `DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION_ON_METHOD` `DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION_ON_PACKAGE` `DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION_ON_TYPE`

org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ANNOTATION_DECLARATION: Use `DefaultCodeFormatterConstants.FORMATTER_KEEP_ANNOTATION_DECLARATION_ON_ONE_LINE` instead.
org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ANONYMOUS_TYPE_DECLARATION: Use `DefaultCodeFormatterConstants.FORMATTER_KEEP_ANONYMOUS_TYPE_DECLARATION_ON_ONE_LINE` instead.

org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_IN_EMPTY_BLOCK

Use `DefaultCodeFormatterConstants.FORMATTER_KEEP_IF_THEN_BODY_BLOCK_ON_ONE_LINE`, `DefaultCodeFormatterConstants.FORMATTER_KEEP_LOOP_BODY_BLOCK_ON_ONE_LINE`, `DefaultCodeFormatterConstants.FORMATTER_KEEP_CODE_BLOCK_ON_ONE_LINE`, and `DefaultCodeFormatterConstants.FORMATTER_KEEP_LAMBDA_BODY_BLOCK_ON_ONE_LINE` instead.

org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ENUM_CONSTANT: Use `DefaultCodeFormatterConstants.FORMATTER_KEEP_ENUM_CONSTANT_DECLARATION_ON_ONE_LINE` instead.
org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ENUM_DECLARATION: Use `DefaultCodeFormatterConstants.FORMATTER_KEEP_ENUM_DECLARATION_ON_ONE_LINE` instead.
org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_IN_EMPTY_METHOD_BODY: Use `DefaultCodeFormatterConstants.FORMATTER_KEEP_METHOD_BODY_ON_ONE_LINE` instead.
org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_IN_EMPTY_TYPE_DECLARATION: Use `DefaultCodeFormatterConstants.FORMATTER_KEEP_TYPE_DECLARATION_ON_ONE_LINE` instead.

org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_AFTER_BINARY_OPERATOR

Use the new settings instead: `DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_AFTER_MULTIPLICATIVE_OPERATOR`, `DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_AFTER_ADDITIVE_OPERATOR`, `DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_AFTER_STRING_CONCATENATION`, `DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_AFTER_SHIFT_OPERATOR`, `DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_AFTER_RELATIONAL_OPERATOR`, `DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_AFTER_BITWISE_OPERATOR`, `DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_AFTER_LOGICAL_OPERATOR`

org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_BEFORE_BINARY_OPERATOR

Use the new settings instead: `DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_BEFORE_MULTIPLICATIVE_OPERATOR`, `DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_BEFORE_ADDITIVE_OPERATOR`, `DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_BEFORE_STRING_CONCATENATION`, `DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_BEFORE_SHIFT_OPERATOR`, `DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_BEFORE_RELATIONAL_OPERATOR`, `DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_BEFORE_BITWISE_OPERATOR`, `DefaultCodeFormatterConstants.FORMATTER_INSERT_SPACE_BEFORE_LOGICAL_OPERATOR`

org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants.FORMATTER_WRAP_BEFORE_BINARY_OPERATOR

Use the new options instead: `DefaultCodeFormatterConstants.FORMATTER_WRAP_BEFORE_MULTIPLICATIVE_OPERATOR`, `DefaultCodeFormatterConstants.FORMATTER_WRAP_BEFORE_ADDITIVE_OPERATOR`, `DefaultCodeFormatterConstants.FORMATTER_WRAP_BEFORE_STRING_CONCATENATION`, `DefaultCodeFormatterConstants.FORMATTER_WRAP_BEFORE_BITWISE_OPERATOR`, `DefaultCodeFormatterConstants.FORMATTER_WRAP_BEFORE_LOGICAL_OPERATOR`

org.eclipse.jdt.core.IJavaElementDelta.F_CLASSPATH_REORDER: Use `IJavaElementDelta.F_REORDER` instead.
org.eclipse.jdt.core.JavaCore.COMPILER_PB_BOOLEAN_METHOD_THROWING_EXCEPTION: - this option has no effect
org.eclipse.jdt.core.JavaCore.COMPILER_PB_INCONSISTENT_NULL_CHECK: Use `JavaCore.COMPILER_PB_NULL_REFERENCE` instead.
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.COMPILER_PB_UNSAFE_TYPE_OPERATION: Use `JavaCore.COMPILER_PB_UNCHECKED_TYPE_OPERATION` instead.
org.eclipse.jdt.core.JavaCore.DEFAULT_TASK_PRIORITY: Use `JavaCore.DEFAULT_TASK_PRIORITIES` instead.
org.eclipse.jdt.core.JavaCore.DEFAULT_TASK_TAG: Use `JavaCore.DEFAULT_TASK_TAGS` 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_BEFORE_CATCH_IN_TRY_STATEMENT`, `DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_BEFORE_ELSE_IN_IF_STATEMENT`, `DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_BEFORE_FINALLY_IN_TRY_STATEMENT`, `DefaultCodeFormatterConstants.FORMATTER_INSERT_NEW_LINE_BEFORE_WHILE_IN_DO_STATEMENT` 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.core.refactoring.IJavaRefactorings.RENAME_RESOURCE: Since 1.2. Use `RenameResourceDescriptor.ID` instead.
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.core.search.IJavaSearchConstants.EXACT_MATCH: Use `SearchPattern.R_EXACT_MATCH` instead.
org.eclipse.jdt.core.search.IJavaSearchConstants.PATTERN_MATCH: Use `SearchPattern.R_PATTERN_MATCH` instead.
org.eclipse.jdt.core.search.IJavaSearchConstants.PREFIX_MATCH: Use `SearchPattern.R_PREFIX_MATCH` instead.
org.eclipse.jdt.core.search.IJavaSearchResultCollector.EXACT_MATCH: Use `SearchMatch.A_ACCURATE` instead.
org.eclipse.jdt.core.search.IJavaSearchResultCollector.POTENTIAL_MATCH: Use `SearchMatch.A_INACCURATE` instead.
org.eclipse.jdt.launching.IJavaLaunchConfigurationConstants.ATTR_VM_INSTALL_NAME: use `ATTR_JRE_CONTAINER_PATH`
org.eclipse.jdt.launching.IJavaLaunchConfigurationConstants.ATTR_VM_INSTALL_TYPE: use `ATTR_JRE_CONTAINER_PATH`
org.eclipse.jdt.launching.JavaRuntime.ATTR_CMDLINE: - use `IProcess.ATTR_CMDLINE`
org.eclipse.jdt.ui.actions.IJavaEditorActionDefinitionIds.CORRECTION_ASSIST_PROPOSALS: As of 3.2, replaced by `ITextEditorActionDefinitionIds.QUICK_ASSIST`
org.eclipse.jdt.ui.actions.IJavaEditorActionDefinitionIds.FIND_STRINGS_TO_EXTERNALIZE: Use `IJavaEditorActionDefinitionIds.EXTERNALIZE_STRINGS` instead
org.eclipse.jdt.ui.actions.IJavaEditorActionDefinitionIds.INLINE_LOCAL_VARIABLE: Use INLINE
org.eclipse.jdt.ui.actions.IJavaEditorActionDefinitionIds.OPEN_EXTERNAL_JAVADOC: As of 3.6, replaced by `IJavaEditorActionDefinitionIds.OPEN_ATTACHED_JAVADOC`
org.eclipse.jdt.ui.actions.IJavaEditorActionDefinitionIds.SHOW_IN_PACKAGE_VIEW: As of 3.5, got replaced by generic Navigate > Show In >
org.eclipse.jdt.ui.actions.IJavaEditorActionDefinitionIds.SHOW_JAVADOC: As of 3.3, replaced by `ITextEditorActionDefinitionIds.SHOW_INFORMATION`
org.eclipse.jdt.ui.actions.IJavaEditorActionDefinitionIds.SHOW_NEXT_PROBLEM: as of 3.0 replaced by `ITextEditorActionDefinitionIds.GOTO_NEXT_ANNOTATION`
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.actions.JdtActionConstants.FIND_STRINGS_TO_EXTERNALIZE: Use `JdtActionConstants.EXTERNALIZE_STRINGS` instead
org.eclipse.jdt.ui.actions.JdtActionConstants.INLINE_TEMP: Use INLINE
org.eclipse.jdt.ui.actions.JdtActionConstants.OPEN_EXTERNAL_JAVA_DOC: As of 3.6, replaced by `JdtActionConstants.OPEN_ATTACHED_JAVA_DOC`
org.eclipse.jdt.ui.actions.JdtActionConstants.SHOW_JAVA_DOC: As of 3.3, replaced by `ITextEditorActionConstants.SHOW_INFORMATION`
org.eclipse.jdt.ui.IJavaElementSearchConstants.CONSIDER_TYPES: use CONSIDER_ALL_TYPES or CONSIDER_CLASSES_AND_INTERFACES instead
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.JavaElementLabelProvider.SHOW_POSTIFIX_QUALIFICATION: SHOW_POST_QUALIFIED instead
org.eclipse.jdt.ui.JavaUI.ATTR_CMDLINE: As of 1.0
org.eclipse.jdt.ui.PreferenceConstants.APPEARANCE_OVERRIDE_INDICATOR: Override Indicator is now controlled on the platform's decorator preference page
org.eclipse.jdt.ui.PreferenceConstants.CODEASSIST_ORDER_PROPOSALS: use `PreferenceConstants.CODEASSIST_SORTER` instead
org.eclipse.jdt.ui.PreferenceConstants.CODEASSIST_PROPOSALS_BACKGROUND: As of 3.4, replaced by `JFacePreferences.CONTENT_ASSIST_BACKGROUND_COLOR`,
org.eclipse.jdt.ui.PreferenceConstants.CODEASSIST_PROPOSALS_FOREGROUND: As of 3.4, replaced by `JFacePreferences.CONTENT_ASSIST_FOREGROUND_COLOR`,
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.ui.PreferenceConstants.EDITOR_ALT_SHIFT_HOVER: As of 3.0, replaced by `PreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_BACKGROUND_COLOR: As of 3.1, replaced by `AbstractTextEditor.PREFERENCE_COLOR_BACKGROUND`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_BACKGROUND_DEFAULT_COLOR: As of 3.1, replaced by `AbstractTextEditor.PREFERENCE_COLOR_BACKGROUND_SYSTEM_DEFAULT`
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_BROWSER_LIKE_LINKS: As of 3.1, replaced by `AbstractDecoratedTextEditorPreferenceConstants.EDITOR_HYPERLINKS_ENABLED`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_BROWSER_LIKE_LINKS_KEY_MODIFIER: As of 3.1, replaced by `AbstractDecoratedTextEditorPreferenceConstants.EDITOR_HYPERLINK_KEY_MODIFIER`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_BROWSER_LIKE_LINKS_KEY_MODIFIER_MASK: As of 3.1, replaced by `AbstractDecoratedTextEditorPreferenceConstants.EDITOR_HYPERLINK_KEY_MODIFIER_MASK`
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_DISABLE_OVERWRITE_MODE: as of 3.1 replaced by `AbstractDecoratedTextEditorPreferenceConstants.EDITOR_DISABLE_OVERWRITE_MODE`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_ERROR_INDICATION_IN_OVERVIEW_RULER: as of 3.0 replaced by `MarkerAnnotationPreferences`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_FIND_SCOPE_COLOR: As of 3.2, use `AbstractTextEditor.PREFERENCE_COLOR_FIND_SCOPE` instead}
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_FOREGROUND_COLOR: As of 3.1, replaced by `AbstractTextEditor.PREFERENCE_COLOR_FOREGROUND`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_FOREGROUND_DEFAULT_COLOR: As of 3.1, replaced by `AbstractTextEditor.PREFERENCE_COLOR_FOREGROUND_SYSTEM_DEFAULT`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_JAVA_ANNOTATION_BOLD: the annotation highlighting has been replaced by a semantic highlighting, see `SemanticHighlightings.ANNOTATION`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_JAVA_ANNOTATION_COLOR: the annotation highlighting has been replaced by a semantic highlighting, see `SemanticHighlightings.ANNOTATION`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_JAVA_ANNOTATION_ITALIC: the annotation highlighting has been replaced by a semantic highlighting, see `SemanticHighlightings.ANNOTATION`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_JAVA_ANNOTATION_STRIKETHROUGH: the annotation highlighting has been replaced by a semantic highlighting, see `SemanticHighlightings.ANNOTATION`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_JAVA_ANNOTATION_UNDERLINE: the annotation highlighting has been replaced by a semantic highlighting, see `SemanticHighlightings.ANNOTATION`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_JAVA_METHOD_NAME_BOLD: the method name highlighting has been replaced by a semantic highlighting, see `SemanticHighlightings.METHOD`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_JAVA_METHOD_NAME_COLOR: the method name highlighting has been replaced by a semantic highlighting, see `SemanticHighlightings.METHOD`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_JAVA_METHOD_NAME_ITALIC: the method name highlighting has been replaced by a semantic highlighting, see `SemanticHighlightings.METHOD`
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_LINK_COLOR: As of 3.1, replaced by `AbstractDecoratedTextEditorPreferenceConstants.EDITOR_HYPERLINK_COLOR`
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_SEMANTIC_HIGHLIGHTING_ENABLED: As of 3.1, this preference is not used or set any longer; see `SemanticHighlightings.affectsEnablement(IPreferenceStore, org.eclipse.jface.util.PropertyChangeEvent)`
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_SHOW_TEXT_HOVER_AFFORDANCE: As of 3.3, replaced by `AbstractDecoratedTextEditorPreferenceConstants.EDITOR_SHOW_TEXT_HOVER_AFFORDANCE`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_SMART_HOME_END: as of 3.3 replaced by `AbstractDecoratedTextEditorPreferenceConstants.EDITOR_SMART_HOME_END`
org.eclipse.jdt.ui.PreferenceConstants.EDITOR_SPACES_FOR_TABS: As of 3.1 replaced by the formatter setting defined in `DefaultCodeFormatterConstants.FORMATTER_TAB_CHAR`
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: as of 3.0 replaced by `MarkerAnnotationPreferences`
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.ui.PreferenceConstants.FORMATTER_COMMENT_CLEARBLANKLINES: As of 3.1, replaced by `DefaultCodeFormatterConstants.FORMATTER_COMMENT_CLEAR_BLANK_LINES`
org.eclipse.jdt.ui.PreferenceConstants.FORMATTER_COMMENT_FORMAT: As of 3.1, replaced by `DefaultCodeFormatterConstants.FORMATTER_COMMENT_FORMAT`
org.eclipse.jdt.ui.PreferenceConstants.FORMATTER_COMMENT_FORMATHEADER: As of 3.1, replaced by `DefaultCodeFormatterConstants.FORMATTER_COMMENT_FORMAT_HEADER`
org.eclipse.jdt.ui.PreferenceConstants.FORMATTER_COMMENT_FORMATHTML: As of 3.1, replaced by `DefaultCodeFormatterConstants.FORMATTER_COMMENT_FORMAT_HTML`
org.eclipse.jdt.ui.PreferenceConstants.FORMATTER_COMMENT_FORMATSOURCE: As of 3.1, replaced by `DefaultCodeFormatterConstants.FORMATTER_COMMENT_FORMAT_SOURCE`
org.eclipse.jdt.ui.PreferenceConstants.FORMATTER_COMMENT_INDENTPARAMETERDESCRIPTION: As of 3.1, replaced by `DefaultCodeFormatterConstants.FORMATTER_COMMENT_INDENT_PARAMETER_DESCRIPTION`
org.eclipse.jdt.ui.PreferenceConstants.FORMATTER_COMMENT_INDENTROOTTAGS: As of 3.1, replaced by `DefaultCodeFormatterConstants.FORMATTER_COMMENT_INDENT_ROOT_TAGS`
org.eclipse.jdt.ui.PreferenceConstants.FORMATTER_COMMENT_LINELENGTH: As of 3.1, replaced by `DefaultCodeFormatterConstants.FORMATTER_COMMENT_LINE_LENGTH`
org.eclipse.jdt.ui.PreferenceConstants.FORMATTER_COMMENT_NEWLINEFORPARAMETER: As of 3.1, replaced by `DefaultCodeFormatterConstants.FORMATTER_COMMENT_INSERT_NEW_LINE_FOR_PARAMETER`
org.eclipse.jdt.ui.PreferenceConstants.FORMATTER_COMMENT_SEPARATEROOTTAGS: As of 3.1, replaced by `DefaultCodeFormatterConstants.FORMATTER_COMMENT_INSERT_EMPTY_LINE_BEFORE_ROOT_TAGS`
org.eclipse.jdt.ui.PreferenceConstants.ID_PROBLEM_HOVER: as of 3.0, this hover is no longer available
org.eclipse.jdt.ui.PreferenceConstants.LINK_PACKAGES_TO_EDITOR: Since 3.3. Not used anymore. Package view always restores with the last recently used setting.
org.eclipse.jdt.ui.PreferenceConstants.LINK_TYPEHIERARCHY_TO_EDITOR: Since 3.3. Not used anymore. Type hierarchy view always restores with the last recently used setting.
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.PreferenceConstants.SPELLING_CHECK_SPELLING: since 3.1, use `SpellingService.PREFERENCE_SPELLING_ENABLED` and `SpellingService.PREFERENCE_SPELLING_ENGINE`
org.eclipse.jdt.ui.PreferenceConstants.UPDATE_JAVA_VIEWS: Since 3.0, views now always update while editing
org.eclipse.jdt.ui.PreferenceConstants.UPDATE_ON_SAVE: Since 3.0, views now always update while editing
org.eclipse.jdt.ui.PreferenceConstants.UPDATE_WHILE_EDITING: 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.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.text.IJavaColorConstants.JAVA_ANNOTATION: replaced as of 3.2 by an equivalent semantic highlighting, see `SemanticHighlightings.ANNOTATION`
org.eclipse.jdt.ui.text.IJavaColorConstants.JAVA_METHOD_NAME: replaced as of 3.1 by an equivalent semantic highlighting, see `SemanticHighlightings.METHOD`
org.eclipse.jdt.ui.text.IJavaColorConstants.JAVA_TYPE: no longer used, replaced by `JAVA_KEYWORD`
org.eclipse.jdt.ui.text.JavaSourceViewerConfiguration.PREFERENCE_TAB_WIDTH: As of 3.0, replaced by `AbstractDecoratedTextEditorPreferenceConstants.EDITOR_TAB_WIDTH`
org.eclipse.jdt.ui.text.JavaSourceViewerConfiguration.SPACES_FOR_TABS: as of 3.1 use `DefaultCodeFormatterConstants.FORMATTER_TAB_CHAR`

Methods
org.eclipse.jdt.apt.core.util.AptConfig.getProcessorOptions​(IJavaProject): Use `AptConfig.getProcessorOptions(IJavaProject, boolean)` or `AptConfig.getRawProcessorOptions(IJavaProject)`
org.eclipse.jdt.core.BindingKey.createWilcardTypeBindingKey​(String, char): This method is missing crucial information necessary for proper wildcard binding key creation.
org.eclipse.jdt.core.compiler.ReconcileContext.getAST3(): JLS3 has been deprecated. This method has been replaced by `ReconcileContext.getAST4()` which returns an AST with JLS4 level.
org.eclipse.jdt.core.compiler.ReconcileContext.getAST4(): JLS4 has been deprecated. This method has been replaced by `ReconcileContext.getAST8()` which returns an AST with JLS8 level.
org.eclipse.jdt.core.compiler.ReconcileContext.getAST8(): JLS8 has been deprecated. This method has been replaced by `ReconcileContext.getAST(int)` which returns an AST with the given level.
org.eclipse.jdt.core.dom.ArrayType.getComponentType(): In the JLS8 API, the recursive structure is not valid.
org.eclipse.jdt.core.dom.ArrayType.setComponentType​(Type): In the JLS8 API, the recursive structure is not valid.
org.eclipse.jdt.core.dom.AST.convertCompilationUnit​(int, CompilationUnitDeclaration, char[], Map, boolean, CompilationUnit, int, IProgressMonitor): Use org.eclipse.jdt.core.dom.AST.convertCompilationUnit(int, CompilationUnitDeclaration, Map, boolean, CompilationUnit, int, IProgressMonitor) instead
org.eclipse.jdt.core.dom.AST.parseCompilationUnit​(char[]): Use `ASTParser` instead.
org.eclipse.jdt.core.dom.BodyDeclaration.setModifiers​(int): In the JLS3 API, this method is replaced by `BodyDeclaration.modifiers()`, which contains a list of `Modifier` nodes.
org.eclipse.jdt.core.dom.ClassInstanceCreation.getName(): In the JLS3 API, this method is replaced by `ClassInstanceCreation.getType()`, which returns a `Type` instead of a `Name`.
org.eclipse.jdt.core.dom.ClassInstanceCreation.setName​(Name): In the JLS3 API, this method is replaced by `ClassInstanceCreation.setType(Type)`, which expects a `Type` instead of a `Name`.
org.eclipse.jdt.core.dom.CompilationUnit.lineNumber​(int): Use getLineNumber(int) instead. Be careful to handle the negative values.
org.eclipse.jdt.core.dom.ITypeBinding.getDeclaredModifiers(): Use `ITypeBinding.getModifiers()` instead. This method was never implemented properly and historically has simply delegated to the method `getModifiers`. Clients should call `getModifiers` method directly.
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.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.core.dom.Message.getSourcePosition(): Use `Message.getStartPosition()` instead.
org.eclipse.jdt.core.dom.MethodDeclaration.getReturnType(): In the JLS3 API, this method is replaced by `MethodDeclaration.getReturnType2()`, which may return `null`.
org.eclipse.jdt.core.dom.MethodDeclaration.setExtraDimensions​(int): In the JLS8 API, this method is replaced by `MethodDeclaration.extraDimensions()` which contains a list of `Dimension` nodes.
org.eclipse.jdt.core.dom.MethodDeclaration.setReturnType​(Type): In the JLS3 API, this method is replaced by `MethodDeclaration.setReturnType2(Type)`, which accepts `null`.
org.eclipse.jdt.core.dom.MethodDeclaration.thrownExceptions(): In the JLS8 API, this method is replaced by `MethodDeclaration.thrownExceptionTypes()`.
org.eclipse.jdt.core.dom.SingleVariableDeclaration.setModifiers​(int): In the JLS3 API, this method is replaced by `SingleVariableDeclaration.modifiers()` which contains a list of a `Modifier` nodes.

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.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.core.dom.TypeDeclaration.getSuperclass(): In the JLS3 API, this method is replaced by `TypeDeclaration.getSuperclassType()`, which returns a `Type` instead of a `Name`.
org.eclipse.jdt.core.dom.TypeDeclaration.setSuperclass​(Name): In the JLS3 API, this method is replaced by `TypeDeclaration.setSuperclassType(Type)`, which expects a `Type` instead of a `Name`.
org.eclipse.jdt.core.dom.TypeDeclaration.superInterfaces(): In the JLS3 API, this method is replaced by `TypeDeclaration.superInterfaceTypes()`.
org.eclipse.jdt.core.dom.TypeDeclarationStatement.getTypeDeclaration(): In the JLS3 API, this method is replaced by `TypeDeclarationStatement.getDeclaration()`, which returns `AbstractTypeDeclaration` instead of `TypeDeclaration`.
org.eclipse.jdt.core.dom.TypeDeclarationStatement.setTypeDeclaration​(TypeDeclaration): In the JLS3 API, this method is replaced by `TypeDeclarationStatement.setDeclaration(AbstractTypeDeclaration)` which takes `AbstractTypeDeclaration` instead of `TypeDeclaration`.
org.eclipse.jdt.core.dom.VariableDeclaration.getExtraDimensionsProperty(): In JLS8 and later, use `VariableDeclaration.getExtraDimensions2Property()` instead.
org.eclipse.jdt.core.dom.VariableDeclaration.setExtraDimensions​(int): In the JLS8 API, this method is replaced by `VariableDeclaration.extraDimensions()` which contains a list of `Dimension` nodes.
org.eclipse.jdt.core.dom.VariableDeclarationExpression.setModifiers​(int): In the JLS3 API, this method is replaced by `VariableDeclarationExpression.modifiers()` which contains a list of a `Modifier` nodes.
org.eclipse.jdt.core.dom.VariableDeclarationStatement.setModifiers​(int): In the JLS3 API, this method is replaced by `VariableDeclarationStatement.modifiers()` which contains a list of a `Modifier` nodes.
org.eclipse.jdt.core.eval.IEvaluationContext.codeComplete​(String, int, ICompletionRequestor): Use `IEvaluationContext.codeComplete(String,int,CompletionRequestor)` instead.
org.eclipse.jdt.core.IClassFile.becomeWorkingCopy​(IProblemRequestor, WorkingCopyOwner, IProgressMonitor): Use `ITypeRoot.getWorkingCopy(WorkingCopyOwner, IProgressMonitor)` instead. Note that if this deprecated method is used, problems will be reported to the given problem requestor as well as the problem requestor returned by the working copy owner (if not null).
org.eclipse.jdt.core.IClassFile.getType(): should only be used as `IOrdinaryClassFile.getType()`.
org.eclipse.jdt.core.IClassFile.getWorkingCopy​(IProgressMonitor, IBufferFactory): Use `ITypeRoot.getWorkingCopy(WorkingCopyOwner, IProgressMonitor)` instead
org.eclipse.jdt.core.IClasspathEntry.getResolvedEntry(): Use `JavaCore.getResolvedClasspathEntry(IClasspathEntry)` instead
org.eclipse.jdt.core.ICodeAssist.codeComplete​(int, ICodeCompletionRequestor): Use `ICodeAssist.codeComplete(int, ICompletionRequestor)` instead.
org.eclipse.jdt.core.ICompilationUnit.becomeWorkingCopy​(IProblemRequestor, IProgressMonitor): Use `ICompilationUnit.becomeWorkingCopy(IProgressMonitor)` instead. Note that if this deprecated method is used, problems will be reported to the given problem requestor as well as the problem requestor returned by the working copy owner (if not null).
org.eclipse.jdt.core.ICompilationUnit.getWorkingCopy​(WorkingCopyOwner, IProblemRequestor, IProgressMonitor): Use `ITypeRoot.getWorkingCopy(WorkingCopyOwner, IProgressMonitor)` instead. Note that if this deprecated method is used, problems will be reported on the passed problem requester as well as on the problem requestor returned by the working copy owner (if not null).
org.eclipse.jdt.core.ICompletionRequestor.acceptAnonymousType​(char[], char[], char[][], char[][], char[][], char[], int, int, int, int): Use `CompletionRequestor.accept(CompletionProposal)` instead.
org.eclipse.jdt.core.ICompletionRequestor.acceptClass​(char[], char[], char[], int, int, int, int): Use `CompletionRequestor.accept(CompletionProposal)` instead.
org.eclipse.jdt.core.ICompletionRequestor.acceptError​(IProblem): Use `CompletionRequestor.completionFailure(IProblem)` instead.
org.eclipse.jdt.core.ICompletionRequestor.acceptField​(char[], char[], char[], char[], char[], char[], int, int, int, int): Use `CompletionRequestor.accept(CompletionProposal)` instead.
org.eclipse.jdt.core.ICompletionRequestor.acceptInterface​(char[], char[], char[], int, int, int, int): Use `CompletionRequestor.accept(CompletionProposal)` instead.
org.eclipse.jdt.core.ICompletionRequestor.acceptKeyword​(char[], int, int, int): Use `CompletionRequestor.accept(CompletionProposal)` instead.
org.eclipse.jdt.core.ICompletionRequestor.acceptLabel​(char[], int, int, int): Use `CompletionRequestor.accept(CompletionProposal)` instead.
org.eclipse.jdt.core.ICompletionRequestor.acceptLocalVariable​(char[], char[], char[], int, int, int, int): Use `CompletionRequestor.accept(CompletionProposal)` instead.
org.eclipse.jdt.core.ICompletionRequestor.acceptMethod​(char[], char[], char[], char[][], char[][], char[][], char[], char[], char[], int, int, int, int): Use `CompletionRequestor.accept(CompletionProposal)` instead.
org.eclipse.jdt.core.ICompletionRequestor.acceptMethodDeclaration​(char[], char[], char[], char[][], char[][], char[][], char[], char[], char[], int, int, int, int): Use `CompletionRequestor.accept(CompletionProposal)` instead.
org.eclipse.jdt.core.ICompletionRequestor.acceptModifier​(char[], int, int, int): Use `CompletionRequestor.accept(CompletionProposal)` instead.
org.eclipse.jdt.core.ICompletionRequestor.acceptPackage​(char[], char[], int, int, int): Use `CompletionRequestor.accept(CompletionProposal)` instead.
org.eclipse.jdt.core.ICompletionRequestor.acceptType​(char[], char[], char[], int, int, int): Use `CompletionRequestor.accept(CompletionProposal)` instead.
org.eclipse.jdt.core.ICompletionRequestor.acceptVariableName​(char[], char[], char[], char[], int, int, int): Use `CompletionRequestor.accept(CompletionProposal)` instead.
org.eclipse.jdt.core.IJavaModelStatus.getString(): Use `IStatus.getMessage()` instead
org.eclipse.jdt.core.IJavaProject.getPackageFragmentRoots​(IClasspathEntry): Use `IJavaProject.findPackageFragmentRoots(IClasspathEntry)` instead
org.eclipse.jdt.core.IMethod.getTypeParameterSignatures(): Use `IMethod.getTypeParameters()` instead
org.eclipse.jdt.core.IPackageFragment.getClassFiles(): Clients are advised to specifically use either `IPackageFragment.getOrdinaryClassFiles()` or `IPackageFragment.getAllClassFiles()` to express their intent.
org.eclipse.jdt.core.IType.codeComplete​(char[], int, int, char[][], char[][], int[], boolean, ICompletionRequestor): Use `IType.codeComplete(char[],int,int,char[][],char[][],int[],boolean,CompletionRequestor)` instead.
org.eclipse.jdt.core.IType.newSupertypeHierarchy​(IWorkingCopy[], IProgressMonitor): Use `IType.newSupertypeHierarchy(ICompilationUnit[], IProgressMonitor)` instead
org.eclipse.jdt.core.IType.newTypeHierarchy​(IWorkingCopy[], IProgressMonitor): Use `IType.newTypeHierarchy(ICompilationUnit[], IProgressMonitor)` instead
org.eclipse.jdt.core.IWorkingCopy.commit​(boolean, IProgressMonitor): Use `ICompilationUnit.commitWorkingCopy(boolean, IProgressMonitor)` instead.
org.eclipse.jdt.core.IWorkingCopy.destroy(): Use `ICompilationUnit.discardWorkingCopy()` instead.
org.eclipse.jdt.core.IWorkingCopy.findElements​(IJavaElement): Use `ICompilationUnit.findElements(IJavaElement)` instead.
org.eclipse.jdt.core.IWorkingCopy.findPrimaryType(): Use `ITypeRoot.findPrimaryType()` instead.
org.eclipse.jdt.core.IWorkingCopy.findSharedWorkingCopy​(IBufferFactory): Use `ICompilationUnit.findWorkingCopy(WorkingCopyOwner)` instead.
org.eclipse.jdt.core.IWorkingCopy.getOriginal​(IJavaElement): Use `IJavaElement.getPrimaryElement()` instead.
org.eclipse.jdt.core.IWorkingCopy.getOriginalElement(): Use `IJavaElement.getPrimaryElement()` instead.
org.eclipse.jdt.core.IWorkingCopy.getSharedWorkingCopy​(IProgressMonitor, IBufferFactory, IProblemRequestor): Use `ICompilationUnit.getWorkingCopy(WorkingCopyOwner, IProblemRequestor, IProgressMonitor)` instead.
org.eclipse.jdt.core.IWorkingCopy.getWorkingCopy(): Use `ICompilationUnit.getWorkingCopy(IProgressMonitor)` instead.
org.eclipse.jdt.core.IWorkingCopy.isBasedOn​(IResource): Use `ICompilationUnit.hasResourceChanged()` instead.
org.eclipse.jdt.core.IWorkingCopy.isWorkingCopy(): Use `ICompilationUnit.isWorkingCopy()` instead.
org.eclipse.jdt.core.IWorkingCopy.reconcile(): Use `ICompilationUnit.reconcile(int, boolean, WorkingCopyOwner, IProgressMonitor)` instead.
org.eclipse.jdt.core.IWorkingCopy.restore(): Use `ICompilationUnit.restore()` instead.
org.eclipse.jdt.core.JavaConventions.isOverlappingRoots​(IPath, IPath): Overlapping roots are allowed in 2.1
org.eclipse.jdt.core.JavaConventions.validateClassFileName​(String): Use `JavaConventions.validateClassFileName(String id, String sourceLevel, String complianceLevel)` instead
org.eclipse.jdt.core.JavaConventions.validateCompilationUnitName​(String): Use `JavaConventions.validateCompilationUnitName(String id, String sourceLevel, String complianceLevel)` instead
org.eclipse.jdt.core.JavaConventions.validateFieldName​(String): Use `JavaConventions.validateFieldName(String id, String sourceLevel, String complianceLevel)` instead
org.eclipse.jdt.core.JavaConventions.validateIdentifier​(String): Use `JavaConventions.validateIdentifier(String id, String sourceLevel, String complianceLevel)` instead
org.eclipse.jdt.core.JavaConventions.validateImportDeclaration​(String): Use `JavaConventions.validateImportDeclaration(String id, String sourceLevel, String complianceLevel)` instead
org.eclipse.jdt.core.JavaConventions.validateJavaTypeName​(String): Use `JavaConventions.validateJavaTypeName(String id, String sourceLevel, String complianceLevel)` instead
org.eclipse.jdt.core.JavaConventions.validateMethodName​(String): Use `JavaConventions.validateMethodName(String id, String sourceLevel, String complianceLevel)` instead
org.eclipse.jdt.core.JavaConventions.validatePackageName​(String): Use `JavaConventions.validatePackageName(String id, String sourceLevel, String complianceLevel)` instead
org.eclipse.jdt.core.JavaConventions.validateTypeVariableName​(String): Use `JavaConventions.validateTypeVariableName(String id, String sourceLevel, String complianceLevel)` instead
org.eclipse.jdt.core.JavaCore.addPreProcessingResourceChangedListener​(IResourceChangeListener): use addPreProcessingResourceChangedListener(listener, IResourceChangeEvent.POST_CHANGE) instead
org.eclipse.jdt.core.JavaCore.getSharedWorkingCopies​(IBufferFactory): Use `JavaCore.getWorkingCopies(WorkingCopyOwner)` instead
org.eclipse.jdt.core.JavaCore.removeClasspathVariable​(String): Use `JavaCore.removeClasspathVariable(String, IProgressMonitor)` instead
org.eclipse.jdt.core.JavaCore.setClasspathVariable​(String, IPath): Use `JavaCore.setClasspathVariable(String, IPath, IProgressMonitor)` instead
org.eclipse.jdt.core.NamingConventions.removePrefixAndSuffixForArgumentName​(IJavaProject, char[]): Use `NamingConventions.getBaseName(int, String, IJavaProject)` instead with `NamingConventions.VK_PARAMETER` as variable kind.
org.eclipse.jdt.core.NamingConventions.removePrefixAndSuffixForFieldName​(IJavaProject, char[], int): Use `NamingConventions.getBaseName(int, String, IJavaProject)` instead with `NamingConventions.VK_INSTANCE_FIELD` or `NamingConventions.VK_STATIC_FIELD` as variable kind.
org.eclipse.jdt.core.NamingConventions.removePrefixAndSuffixForLocalVariableName​(IJavaProject, char[]): Use `NamingConventions.getBaseName(int, String, IJavaProject)` instead with `NamingConventions.VK_LOCAL` as variable kind.
org.eclipse.jdt.core.NamingConventions.suggestArgumentNames​(IJavaProject, char[], char[], int, char[][]): Use `NamingConventions.suggestVariableNames(int, int, String, IJavaProject, int, String[], boolean)` instead with `NamingConventions.VK_PARAMETER` as variable kind.
org.eclipse.jdt.core.NamingConventions.suggestFieldNames​(IJavaProject, char[], char[], int, int, char[][]): Use `NamingConventions.suggestVariableNames(int, int, String, IJavaProject, int, String[], boolean)` instead with `NamingConventions.VK_INSTANCE_FIELD` or `NamingConventions.VK_STATIC_FIELD` as variable kind.
org.eclipse.jdt.core.NamingConventions.suggestLocalVariableNames​(IJavaProject, char[], char[], int, char[][]): Use `NamingConventions.suggestVariableNames(int, int, String, IJavaProject, int, String[], boolean)` instead with `NamingConventions.VK_LOCAL` as variable kind.
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.core.search.IJavaSearchResultCollector.done(): Replaced by `SearchRequestor.endReporting()`.
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.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.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.core.search.SearchEngine.createSearchPattern​(String, int, int, boolean): Use `SearchPattern.createPattern(String, int, int, int)` 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​(char[], char[], int, int, IJavaSearchScope, TypeNameRequestor, int, IProgressMonitor): Use `SearchEngine.searchAllTypeNames(char[], int, char[], int, int, IJavaSearchScope, TypeNameRequestor, 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.search.SearchPattern.createAndPattern​(SearchPattern, SearchPattern): Unfortunately, this functionality is not fully supported yet (see "https://bugs.eclipse.org/bugs/show_bug.cgi?id=142044" for more details). This might be done in a further version...
org.eclipse.jdt.core.ToolFactory.createCodeFormatter(): The extension point has been deprecated, use `ToolFactory.createCodeFormatter(Map)` instead.
org.eclipse.jdt.core.ToolFactory.createDefaultClassFileDisassembler(): Use `ToolFactory.createDefaultClassFileBytesDisassembler()` instead
org.eclipse.jdt.core.ToolFactory.createDefaultCodeFormatter​(Map): Use `ToolFactory.createCodeFormatter(Map)` instead but note the different options
org.eclipse.jdt.core.util.ByteCodeVisitorAdapter._invokedynamic​(int, int, IConstantPoolEntry, IConstantPoolEntry): This has been replaced with `IBytecodeVisitor._invokedynamic(int, int, IConstantPoolEntry)`
org.eclipse.jdt.core.util.CompilationUnitSorter.sort​(ICompilationUnit, int[], Comparator, int, IProgressMonitor): Clients should port their code to use the new JLS3 AST API and call `CompilationUnitSorter.sort(AST.JLS3, compilationUnit, positions, comparator, options, monitor)` instead of using this method.
org.eclipse.jdt.core.util.IBytecodeVisitor._invokedynamic​(int, int, IConstantPoolEntry, IConstantPoolEntry): This has been replaced with `IBytecodeVisitor._invokedynamic(int, int, IConstantPoolEntry)`
org.eclipse.jdt.core.WorkingCopyOwner.newWorkingCopy​(String, IClasspathEntry[], IProblemRequestor, IProgressMonitor): Use `WorkingCopyOwner.newWorkingCopy(String, IClasspathEntry[], IProgressMonitor)` instead. Note that if this deprecated method is used, problems may be reported twice if the given requestor is not the same as the current working copy owner one.
org.eclipse.jdt.debug.core.IJavaExceptionBreakpoint.getFilters(): Use getExclusionFilters() or getInclusionFilters()
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.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.debug.core.IJavaStackFrame.getDeclaringType(): Use `getReferenceType()` instead, as a method is not restricted to occur in a class. An interface may contain a synthetic class initializer methods. Since 3.1, this method throws a `DebugException` when a stack frame's method is contained in an interface.
org.eclipse.jdt.debug.core.IJavaStackFrame.supportsDropToFrame(): since 3.1, IJavaStackFrame extends org.eclipse.debug.core.IDropToFrame which defines canDropToFrame(). Use this method instead.
org.eclipse.jdt.debug.core.JDIDebugModel.createPatternBreakpoint​(IResource, String, String, int, int, int, int, boolean, Map<String, Object>): use `createStratumBreakpoint` instead
org.eclipse.jdt.debug.core.JDIDebugModel.getPreferences(): the `Preferences` class has been deprecated, use the `IEclipsePreferences` accessors instead
org.eclipse.jdt.debug.core.JDIDebugModel.savePreferences(): the `Preferences` class has been deprecated, use the `IEclipsePreferences` accessors instead
org.eclipse.jdt.debug.eval.ICompiledExpression.getErrors(): use getErrorMessages()
org.eclipse.jdt.debug.eval.IEvaluationResult.getErrors(): use getErrorMessages()
org.eclipse.jdt.junit.JUnitCore.addTestRunListener​(ITestRunListener): As of 3.3, replaced by `JUnitCore.addTestRunListener(TestRunListener)`
org.eclipse.jdt.junit.JUnitCore.removeTestRunListener​(ITestRunListener): As of 3.3, replaced by `JUnitCore.removeTestRunListener(TestRunListener)`
org.eclipse.jdt.junit.launcher.JUnitLaunchConfigurationDelegate.getClasspath​(ILaunchConfiguration): The call to `getClasspath(ILaunchConfiguration)` in `launch(...)` has been replaced with the call to `getClasspathAndModulepath(ILaunchConfiguration)`.
org.eclipse.jdt.junit.wizards.NewTestCaseWizardPageOne.isJUnit4(): use `NewTestCaseWizardPageOne.getJUnitVersion()` instead
org.eclipse.jdt.junit.wizards.NewTestCaseWizardPageOne.setJUnit4​(boolean, boolean): use `NewTestCaseWizardPageOne.setJUnitVersion(JUnitVersion)` and `NewTestCaseWizardPageOne.setEnabled(boolean)` instead
org.eclipse.jdt.launching.AbstractJavaLaunchConfigurationDelegate.getClasspath​(ILaunchConfiguration): use getClasspathAndModulepath
org.eclipse.jdt.launching.IVMInstall.setVMArguments​(String[]): if possible, clients should use setVMArgs(String) on `IVMInstall2` when possible
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.actions.GenerateActionGroup.editorStateChanged(): As of 3.5, this method is no longer called
org.eclipse.jdt.ui.ITypeHierarchyViewPart.getInput(): use getInputElement instead
org.eclipse.jdt.ui.ITypeHierarchyViewPart.setInput​(IType): use setInputElement instead
org.eclipse.jdt.ui.jarpackager.JarPackageData.createJarDescriptionWriter​(OutputStream): Use `JarPackageData.createJarDescriptionWriter(OutputStream, String)` instead
org.eclipse.jdt.ui.jarpackager.JarPackageData.createJarWriter​(Shell): Use `JarPackageData.createJarWriter3(Shell)` instead
org.eclipse.jdt.ui.jarpackager.JarPackageData.createJarWriter3​(Shell): use `JarPackageData.createPlainJarBuilder()` instead
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.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.JavadocContentAccess.getHTMLContentReader​(IMember, boolean): As of 3.2, replaced by `JavadocContentAccess.getHTMLContentReader(IMember, boolean, boolean)`
org.eclipse.jdt.ui.JavaElementSorter.getCollator(): The method is not intended to be used by clients.
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.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.JavaUI.getLibraryJavadocLocation​(IPath): Javadoc is now attached to the classpath entry. Use `JavaUI.getJavadocBaseLocation(IJavaElement)` with the archive's `IPackageFragmentRoot` or use `JavaUI.getLibraryJavadocLocation(IClasspathEntry)` with the archive's `IClasspathEntry`.
org.eclipse.jdt.ui.JavaUI.getSharedWorkingCopies(): Use `JavaCore.getWorkingCopies(org.eclipse.jdt.core.WorkingCopyOwner)` instead with `null` as argument for owner.
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.JavaUI.revealInEditor​(IEditorPart, ISourceReference): use `revealInEditor(IEditorPart, IJavaElement)` instead
org.eclipse.jdt.ui.JavaUI.setLibraryJavadocLocation​(IPath, URL): Javadoc is now attached to the classpath entry. Evaluate the libraries classpath entry and reconfigure the Javadoc location there.
org.eclipse.jdt.ui.JavaUI.setLibraryJavadocLocations​(IPath[], URL[]): Javadoc is now attached to the classpath entry. Evaluate the libraries classpath entry and reconfigure the Javadoc location there.
org.eclipse.jdt.ui.OverrideIndicatorLabelDecorator.findInHierarchy​(IType, ITypeHierarchy, String, String[]): Not used anymore. This method is not accurate for methods in generic types.
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.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.
org.eclipse.jdt.ui.text.JavaSourceViewerConfiguration.getPreferenceStore(): As of 3.0
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.ui.text.JavaTextTools.getCodeScanner(): As of 3.0, replaced by `JavaSourceViewerConfiguration.getCodeScanner()`
org.eclipse.jdt.ui.text.JavaTextTools.getJavaDocScanner(): As of 3.0, replaced by `JavaSourceViewerConfiguration.getJavaDocScanner()`
org.eclipse.jdt.ui.text.JavaTextTools.getMultilineCommentScanner(): As of 3.0, replaced by `JavaSourceViewerConfiguration.getMultilineCommentScanner()`
org.eclipse.jdt.ui.text.JavaTextTools.getPartitionManagingPositionCategories(): As of 3.0, replaced by `TextUtilities.computePartitionManagingCategories(IDocument)`
org.eclipse.jdt.ui.text.JavaTextTools.getSinglelineCommentScanner(): As of 3.0, replaced by `JavaSourceViewerConfiguration.getSinglelineCommentScanner()`
org.eclipse.jdt.ui.text.JavaTextTools.getStringScanner(): As of 3.0, replaced by `JavaSourceViewerConfiguration.getStringScanner()`
org.eclipse.jdt.ui.wizards.JavaCapabilityConfigurationPage.createProject​(IProject, IPath, IProgressMonitor): use `JavaCapabilityConfigurationPage.createProject(IProject, URI, IProgressMonitor)` instead.
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.ui.wizards.NewTypeWizardPage.getTemplate​(String, ICompilationUnit): Use getTemplate(String,ICompilationUnit,int)
org.eclipse.jdt.ui.wizards.NewTypeWizardPage.getTypeComment​(ICompilationUnit): Use getTypeComment(ICompilationUnit, String)

Constructors
org.eclipse.jdt.core.dom.AST(): Clients should port their code to use the latest JLS* AST API and call `AST.newAST(AST.JLS9)` instead of using this constructor.
org.eclipse.jdt.core.refactoring.descriptors.RenameLocalVariableDescriptor(): merged into `RenameJavaElementDescriptor`
org.eclipse.jdt.core.search.SearchEngine​(IWorkingCopy[]): Use `SearchEngine(ICompilationUnit[])` instead.
org.eclipse.jdt.ui.actions.OpenExternalJavadocAction​(IWorkbenchSite, ISelectionProvider): Use `SelectionDispatchAction.setSpecialSelectionProvider(ISelectionProvider)` instead.
org.eclipse.jdt.ui.actions.OpenSuperImplementationAction​(IWorkbenchSite, ISelectionProvider): Use `SelectionDispatchAction.setSpecialSelectionProvider(ISelectionProvider)` instead. This API will be removed after 3.2 M5.
org.eclipse.jdt.ui.actions.OpenTypeHierarchyAction​(IWorkbenchSite, ISelectionProvider): Use `SelectionDispatchAction.setSpecialSelectionProvider(ISelectionProvider)` instead. This API will be removed after 3.2 M5.
org.eclipse.jdt.ui.actions.SelectionDispatchAction​(IWorkbenchSite, ISelectionProvider): Use `SelectionDispatchAction.setSpecialSelectionProvider(ISelectionProvider)` instead. This constructor will be removed after 3.2 M5.
org.eclipse.jdt.ui.StandardJavaElementContentProvider​(boolean, boolean): Use `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.
org.eclipse.jdt.ui.text.JavaSourceViewerConfiguration​(JavaTextTools, ITextEditor): As of 3.0, replaced by `JavaSourceViewerConfiguration(IColorManager, IPreferenceStore, ITextEditor, String)`