Deprecated API
Contents
-
ElementDescriptionPlease use CleanUpContext in the futurePlease use CleanUpOptions in the future This class is not intended to be subclassed by clients.Please use CleanUpRequirements in the futurePlease use ICleanUpFix in the futureUse
JarPackageData.createJarWriter3(Shell)
insteaduseJarWriter3
instead.UseJarWriter3
instead which leverages newEFS
support
-
InterfaceDescriptionUse
WorkingCopyOwner
insteadUseCompletionRequestor
instead.UseCodeFormatter
instead (note: options have changed)UseCompletionRequestor
instead.UseICompilationUnit
insteadThe 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.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.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.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.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.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.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.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.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.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.Please use ICleanUpFix in the futureSince 3.0, the classSearchRequestor
replaces this interface.Since 3.0, the classSearchPattern
replaces this interface.Use abstract classTypeNameRequestor
instead.UseClassFileBytesDisassembler
insteaduseIJavaStratumLineBreakpoint
insteadAs of 3.3, replaced byTestRunListener
support has been added toClasspathContainerInitializer
to handle comparison of classpath containers. UseClasspathContainerInitializer.getComparisonID(IPath,IJavaProject)
. When a classpath container implements this interface, this interface is used to determine equality before using the support defined inClasspathContainerInitializer
.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
andorg.eclipse.debug.core.sourcelookup.containers
. This interface has been replaced byorg.eclipse.debug.core.sourcelookup.ISourceContainer
.Please use IRefactoringProcessorIdsCore. Do not update this file.As of 3.2, replaced byorg.eclipse.jdt.ui.javaCompletionProposalComputer
extension-point.
-
ClassDescriptionSubclass
CompletionRequestor
instead.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.Please use CleanUpContext in the futurePlease use CleanUpOptions in the future This class is not intended to be subclassed by clients.Please use CleanUpRequirements in the futuresince 1.2 merged intoRenameJavaElementDescriptor
since 1.2, useRenameResourceDescriptor
fromorg.eclipse.ltk.core.refactoring
instead.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
andorg.eclipse.debug.core.sourcelookup.containers
. This class has been replaced by a dialog in the debug platform -org.eclipse.debug.ui.sourcelookup.SourceLookupDialog
.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
andorg.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"
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 thesourceLocatorId
attribute on a launch configuration type extension.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
andorg.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
.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
andorg.eclipse.debug.core.sourcelookup.containers
. This class has been replaced by the following classes:org.eclipse.debug.core.sourcelookup.containers.ArchiveSourceContainer
andorg.eclipse.debug.core.sourcelookup.containers.ExternalArchiveSourceContainer
.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
andorg.eclipse.debug.core.sourcelookup.containers
. This class has been replaced byorg.eclipse.debug.core.sourcelookup.containers.DirectorySourceContainer
.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
andorg.eclipse.debug.core.sourcelookup.containers
. This class has been replaced byorg.eclipse.jdt.launching.sourcelookup.containers.JavaProjectSourceContainer
.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
andorg.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"
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 thesourceLocatorId
attribute on a launch configuration type extension.In 3.0 this class is now provided by the debug platform. Clients should use the replacement classorg.eclipse.debug.core.sourcelookup.containers.LocalFileStorage
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
andorg.eclipse.debug.core.sourcelookup.containers
. This class has been replaced byorg.eclipse.jdt.launching.sourcelookup.containers.PackageFragmentRootSourceContainer
.In 3.0 this class is provided by the debug platform and clients should use the replacement classorg.eclipse.debug.core.sourcelookup.containers.ZipEntryStorage
.useExternalizeStringsAction
insteadAs of 3.6, replaced byOpenAttachedJavadocAction
As of 3.5, got replaced by generic Navigate > Show In >As of 3.5, got replaced by generic Navigate > Show In >SeeCodeGeneration
useJarWriter3
instead.UseJarWriter3
instead which leverages newEFS
supportuse the StandardJavaElementContentProvider insteaduseJavaElementComparator
instead.UseSharedASTProviderCore
instead.
-
ExceptionsDescriptionThe 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.
-
FieldDescription- problem is no longer generated (code is legite)- problem is no longer generated, use
IProblem.AmbiguousType
instead- problem is no longer generated, useIProblem.CannotAllocateVoidArray
instead- problem is no longer generated, useIProblem.InheritedTypeHidesEnclosingName
instead- problem is no longer generated, useIProblem.InternalTypeNameProvided
instead- problem is no longer generated, useIProblem.UndefinedType
instead- problem is no longer generated, useIProblem.NotVisibleType
instead- problem is no longer generated, useIProblem.AmbiguousType
instead- problem is no longer generated, useIProblem.InheritedTypeHidesEnclosingName
instead- problem is no longer generated, useIProblem.InternalTypeNameProvided
instead- problem is no longer generated, useIProblem.UndefinedType
instead- problem is no longer generated, useIProblem.NotVisibleType
instead- problem is no longer generated, useIProblem.AmbiguousType
instead- problem is no longer generated, useIProblem.InheritedTypeHidesEnclosingName
instead- problem is no longer generated, useIProblem.InternalTypeNameProvided
instead- problem is no longer generated, useIProblem.UndefinedType
instead- problem is no longer generated, useIProblem.NotVisibleType
instead- problem could not be reported, enums cannot be local takes precedence- problem is no longer generated, useIProblem.AmbiguousType
instead- problem is no longer generated, useIProblem.InheritedTypeHidesEnclosingName
instead- problem is no longer generated, useIProblem.InternalTypeNameProvided
instead- problem is no longer generated, useIProblem.NotVisibleType
instead- problem is no longer generated, useIProblem.AmbiguousType
instead- problem is no longer generated, useIProblem.InheritedTypeHidesEnclosingName
instead- problem is no longer generated, useIProblem.InternalTypeNameProvided
instead- problem is no longer generated, useIProblem.UndefinedType
instead- problem is no longer generated, useIProblem.NotVisibleType
instead- problem is no longer generated- problem is no longer generated (implementation issue has been resolved)- problem is no longer generated, useIProblem.RedundantNullCheckOnNonNullLocalVariable
instead- problem is no longer generated, useIProblem.NullLocalVariableReference
,IProblem.RedundantNullCheckOnNullLocalVariable
orIProblem.RedundantLocalVariableNullAssignment
instead- problem is no longer generated, useIProblem.PotentialNullLocalVariableReference
insteadThis problem is no longer reported; number Of functional interface is not an issue, number of abstract methods is.- problem is no longer generatedproblem no longer generated- problem is no longer generated, useIProblem.AmbiguousType
instead- problem is no longer generated, useIProblem.CannotAllocateVoidArray
instead- problem is no longer generated, useIProblem.InheritedTypeHidesEnclosingName
instead- problem is no longer generated, useIProblem.InternalTypeNameProvided
instead- problem is no longer generated, useIProblem.UndefinedType
instead- problem is no longer generated, useIProblem.NotVisibleType
insteadproblem no longer generatedproblem no longer generatedproblem no longer generated- problem is no longer generated, useIProblem.AmbiguousType
instead- problem is no longer generated, useIProblem.InheritedTypeHidesEnclosingName
instead- problem is no longer generated, useIProblem.InternalTypeNameProvided
instead- problem is no longer generated, useIProblem.UndefinedType
instead- problem is no longer generated, useIProblem.NotVisibleType
insteadpreview related error - will be removedpreview related error - will be removedpreview related error - will be removedpreview related error - will be removedpreview related error - will be removedpreview related error - will be removedpreview related error - will be removedpreview related error - will be removedpreview related error - will be removedno longer issued - will be removedno longer issued - will be removedno longer issued - will be removedno longer issued - will be removedno longer issued - will be removedno longer issued - will be removedno longer issued - will be removedno longer issued - will be removedno longer issued - will be removedno longer issued - will be removedno longer issued - will be removedpreview related error - will be removedpreview related error - will be removed- no longer generated, useIProblem.UnnecessaryCast
instead- problem is no longer generated, useIProblem.CannotAllocateVoidArray
insteadWith 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 ofIScanner
).In the JLS8 API, this property is replaced byArrayType.ELEMENT_TYPE_PROPERTY
andArrayType.DIMENSIONS_PROPERTY
.Clients should use theAST.getJLSLatest()
AST API instead.Clients should use theAST.getJLSLatest()
AST API instead.Clients should use theAST.getJLSLatest()
AST API instead.Clients should use theAST.getJLSLatest()
AST API instead.Clients should use theAST.getJLSLatest()
AST API instead.Clients should use theAST.getJLSLatest()
AST API instead.Clients should use theAST.getJLSLatest()
AST API instead.Clients should use theAST.getJLSLatest()
AST API instead.Clients should use theAST.getJLSLatest()
AST API instead.Clients should use theAST.getJLSLatest()
AST API instead.Clients should use theAST.getJLSLatest()
AST API instead.Clients should use theAST.getJLSLatest()
AST API instead.Clients should use theAST.getJLSLatest()
AST API instead.In the JLS3 API, this property is replaced byClassInstanceCreation.TYPE_PROPERTY
.In the JLS3 API, this property is replaced byFieldDeclaration.MODIFIERS2_PROPERTY
.In the JLS3 API, this property is replaced byInitializer.MODIFIERS2_PROPERTY
.Replaced byJavadoc.TAGS_PROPERTY
in the JLS3 API.In JLS8 and later, useMethodDeclaration.EXTRA_DIMENSIONS2_PROPERTY
instead.In the JLS3 API, this property is replaced byMethodDeclaration.MODIFIERS2_PROPERTY
.In the JLS3 API, this property is replaced byMethodDeclaration.RETURN_TYPE2_PROPERTY
.In JLS8 and later, useMethodDeclaration.THROWN_EXCEPTION_TYPES_PROPERTY
instead.use pattern property instead from Java 20 onwardsIn JLS8 and later, useSingleVariableDeclaration.EXTRA_DIMENSIONS2_PROPERTY
instead.In the JLS3 API, this property is replaced bySingleVariableDeclaration.MODIFIERS2_PROPERTY
.In the JLS 12 15.28.1 API, this property is replaced bySwitchCase.EXPRESSIONS2_PROPERTY
.In the JLS9 API, this property is replaced byTryStatement.RESOURCES2_PROPERTY
.In the JLS3 API, this property is replaced byTypeDeclaration.MODIFIERS2_PROPERTY
.In the JLS3 API, this property is replaced byTypeDeclaration.SUPER_INTERFACE_TYPES_PROPERTY
.In the JLS3 API, this property is replaced byTypeDeclaration.SUPERCLASS_TYPE_PROPERTY
.In the JLS3 API, this property is replaced byTypeDeclarationStatement.DECLARATION_PROPERTY
.In the JLS22 API, this property is replaced byVariableDeclaration
.In the JLS3 API, this property is replaced byVariableDeclarationExpression.MODIFIERS2_PROPERTY
.in JLS8 and later, useVariableDeclarationFragment.EXTRA_DIMENSIONS2_PROPERTY
instead.In the JLS3 API, this property is replaced byVariableDeclarationStatement.MODIFIERS2_PROPERTY
.- no longer used, such deltas are now notified during POST_CHANGEUse 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
Use multiple settings for each kind of comments. SeeDefaultCodeFormatterConstants.FORMATTER_COMMENT_FORMAT_BLOCK_COMMENT
,DefaultCodeFormatterConstants.FORMATTER_COMMENT_FORMAT_JAVADOC_COMMENT
andDefaultCodeFormatterConstants.FORMATTER_COMMENT_FORMAT_LINE_COMMENT
.All new options must be enabled to activate old strategyDefaultCodeFormatterConstants.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
All new options must be enabled to activate old strategyDefaultCodeFormatterConstants.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
UseDefaultCodeFormatterConstants.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
, andDefaultCodeFormatterConstants.FORMATTER_KEEP_LAMBDA_BODY_BLOCK_ON_ONE_LINE
instead.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
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
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
UseIJavaElementDelta.F_REORDER
instead.- this option has no effectthis option is implicitly enabled and can't be switched off anymore- this option has no effectUseJavaCore.COMPILER_PB_NULL_REFERENCE
instead.Discontinued since turning off would violate language specs.Discontinued since turning off would violate language specs.UseJavaCore.COMPILER_PB_UNCHECKED_TYPE_OPERATION
instead.UseJavaCore.DEFAULT_TASK_PRIORITIES
instead.UseJavaCore.DEFAULT_TASK_TAGS
instead.UseDefaultCodeFormatterConstants.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.UseDefaultCodeFormatterConstants.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.UseDefaultCodeFormatterConstants.FORMATTER_TAB_CHAR
instead.UseDefaultCodeFormatterConstants.FORMATTER_TAB_SIZE
instead.Since 1.2. UseRenameResourceDescriptor.ID
instead.Use the methods that take the matchMode withoutSearchPattern.R_CASE_SENSITIVE
as a matchRule instead.Use the methods that take the matchMode withSearchPattern.R_CASE_SENSITIVE
as a matchRule instead.UseSearchPattern.R_EXACT_MATCH
instead.UseSearchPattern.R_PATTERN_MATCH
instead.UseSearchPattern.R_PREFIX_MATCH
instead.UseSearchMatch.A_ACCURATE
instead.UseSearchMatch.A_INACCURATE
instead.useATTR_JRE_CONTAINER_PATH
useATTR_JRE_CONTAINER_PATH
- useIProcess.ATTR_CMDLINE
As of 3.2, replaced byITextEditorActionDefinitionIds.QUICK_ASSIST
Use INLINEAs of 3.6, replaced byIJavaEditorActionDefinitionIds.OPEN_ATTACHED_JAVADOC
As of 3.5, got replaced by generic Navigate > Show In >As of 3.3, replaced byITextEditorActionDefinitionIds.SHOW_INFORMATION
as of 3.0 replaced byITextEditorActionDefinitionIds.GOTO_NEXT_ANNOTATION
as of 3.0 replaced byITextEditorActionDefinitionIds.GOTO_PREVIOUS_ANNOTATION
as of 3.0 replaced byITextEditorActionDefinitionIds.TOGGLE_SHOW_SELECTED_ELEMENT_ONLY
UseJdtActionConstants.EXTERNALIZE_STRINGS
insteadUse INLINEAs of 3.6, replaced byJdtActionConstants.OPEN_ATTACHED_JAVA_DOC
As of 3.3, replaced byITextEditorActionConstants.SHOW_INFORMATION
use CONSIDER_ALL_TYPES or CONSIDER_CLASSES_AND_INTERFACES insteadUse SHOW_QUALIFIED or SHOW_ROOT insteadUse SHOW_QUALIFIED insteadSHOW_POST_QUALIFIED insteadUseJavaElementLabels.ALL_CATEGORY2
instead.As of 1.0Override Indicator is now controlled on the platform's decorator preference pageusePreferenceConstants.CODEASSIST_SORTER
insteadAs of 3.4, replaced byJFacePreferences.CONTENT_ASSIST_BACKGROUND_COLOR
,As of 3.4, replaced byJFacePreferences.CONTENT_ASSIST_FOREGROUND_COLOR
,New code template story: user can specify the new file code template.Use CODEGEN_ADD_COMMENTS instead (Name is more precise).New code template story: user can specify the overriding method comment.Use JavaCore preference store (key JavaCore. CODEASSIST_FIELD_PREFIXES and CODEASSIST_STATIC_FIELD_PREFIXES)Use setting from JavaCore preference store (key JavaCore. CODEASSIST_FIELD_SUFFIXES and CODEASSIST_STATIC_FIELD_SUFFIXES)Use JavaCore preference store (key JavaCore. CODEASSIST_FIELD_PREFIXES and CODEASSIST_STATIC_FIELD_PREFIXES)Use JavaCore preference store (key JavaCore. CODEASSIST_FIELD_PREFIXES and CODEASSIST_STATIC_FIELD_PREFIXES)As of 3.0, replaced byPreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS
As of 3.1, replaced byAbstractTextEditor.PREFERENCE_COLOR_BACKGROUND
As of 3.1, replaced byAbstractTextEditor.PREFERENCE_COLOR_BACKGROUND_SYSTEM_DEFAULT
as of 3.0 replaced byMarkerAnnotationPreferences
as of 3.0 replaced byMarkerAnnotationPreferences
as of 3.0 replaced byMarkerAnnotationPreferences
As of 3.1, replaced byAbstractDecoratedTextEditorPreferenceConstants.EDITOR_HYPERLINKS_ENABLED
As of 3.1, replaced byAbstractDecoratedTextEditorPreferenceConstants.EDITOR_HYPERLINK_KEY_MODIFIER
As of 3.1, replaced byAbstractDecoratedTextEditorPreferenceConstants.EDITOR_HYPERLINK_KEY_MODIFIER_MASK
As of 3.0, replaced byPreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS
As of 3.0, replaced byPreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS
As of 3.0, replaced byPreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS
As of 3.0, replaced byPreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS
as of 3.0 replaced byAbstractDecoratedTextEditorPreferenceConstants
as of 3.0 replaced byAbstractDecoratedTextEditorPreferenceConstants
As of 3.0, replaced byPreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS
As of 3.0, replaced byPreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS
as of 3.1 replaced byAbstractDecoratedTextEditorPreferenceConstants.EDITOR_DISABLE_OVERWRITE_MODE
as of 3.0 replaced byMarkerAnnotationPreferences
As of 3.2, useAbstractTextEditor.PREFERENCE_COLOR_FIND_SCOPE
instead}As of 3.1, replaced byAbstractTextEditor.PREFERENCE_COLOR_FOREGROUND
As of 3.1, replaced byAbstractTextEditor.PREFERENCE_COLOR_FOREGROUND_SYSTEM_DEFAULT
the annotation highlighting has been replaced by a semantic highlighting, seeSemanticHighlightings.ANNOTATION
the annotation highlighting has been replaced by a semantic highlighting, seeSemanticHighlightings.ANNOTATION
the annotation highlighting has been replaced by a semantic highlighting, seeSemanticHighlightings.ANNOTATION
the annotation highlighting has been replaced by a semantic highlighting, seeSemanticHighlightings.ANNOTATION
the annotation highlighting has been replaced by a semantic highlighting, seeSemanticHighlightings.ANNOTATION
the method name highlighting has been replaced by a semantic highlighting, seeSemanticHighlightings.METHOD
the method name highlighting has been replaced by a semantic highlighting, seeSemanticHighlightings.METHOD
the method name highlighting has been replaced by a semantic highlighting, seeSemanticHighlightings.METHOD
as of 3.0 replaced byAbstractDecoratedTextEditorPreferenceConstants
as of 3.0 replaced byAbstractDecoratedTextEditorPreferenceConstants
As of 3.1, replaced byAbstractDecoratedTextEditorPreferenceConstants.EDITOR_HYPERLINK_COLOR
not used any longer as the linked positions are displayed as annotationsAs of 3.0, replaced byPreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS
As of 3.0, replaced byPreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS
as of 3.0 replaced byAbstractDecoratedTextEditorPreferenceConstants
as of 3.0 replaced byAbstractDecoratedTextEditorPreferenceConstants
as of 3.0 replaced byAbstractDecoratedTextEditorPreferenceConstants
as of 3.0 replaced byAbstractDecoratedTextEditorPreferenceConstants
as of 3.0 replaced byMarkerAnnotationPreferences
as of 3.0 replaced byMarkerAnnotationPreferences
as of 3.0 replaced byMarkerAnnotationPreferences
as of 3.0 replaced byMarkerAnnotationPreferences
as of 3.0 replaced byMarkerAnnotationPreferences
As of 3.1, this preference is not used or set any longer; seeSemanticHighlightings.affectsEnablement(IPreferenceStore, org.eclipse.jface.util.PropertyChangeEvent)
As of 3.0, replaced byPreferenceConstants.EDITOR_TEXT_HOVER_MODIFIERS
As of 3.3, replaced byAbstractDecoratedTextEditorPreferenceConstants.EDITOR_SHOW_TEXT_HOVER_AFFORDANCE
as of 3.3 replaced byAbstractDecoratedTextEditorPreferenceConstants.EDITOR_SMART_HOME_END
As of 3.1 replaced by the formatter setting defined inDefaultCodeFormatterConstants.FORMATTER_TAB_CHAR
As of 3.0 replaced byAbstractDecoratedTextEditorPreferenceConstants.EDITOR_TAB_WIDTH
as of 3.0 replaced byMarkerAnnotationPreferences
as of 3.0 replaced byMarkerAnnotationPreferences
as of 3.0 replaced byMarkerAnnotationPreferences
as of 3.0 replaced byMarkerAnnotationPreferences
as of 3.0 replaced byMarkerAnnotationPreferences
as of 3.0 replaced byMarkerAnnotationPreferences
as of 3.0 replaced byMarkerAnnotationPreferences
as of 3.0 replaced byMarkerAnnotationPreferences
as of 3.0 replaced byMarkerAnnotationPreferences
As of 3.1, replaced byDefaultCodeFormatterConstants.FORMATTER_COMMENT_CLEAR_BLANK_LINES
As of 3.1, replaced byDefaultCodeFormatterConstants.FORMATTER_COMMENT_FORMAT
As of 3.1, replaced byDefaultCodeFormatterConstants.FORMATTER_COMMENT_FORMAT_HEADER
As of 3.1, replaced byDefaultCodeFormatterConstants.FORMATTER_COMMENT_FORMAT_HTML
As of 3.1, replaced byDefaultCodeFormatterConstants.FORMATTER_COMMENT_FORMAT_SOURCE
As of 3.1, replaced byDefaultCodeFormatterConstants.FORMATTER_COMMENT_INDENT_PARAMETER_DESCRIPTION
As of 3.1, replaced byDefaultCodeFormatterConstants.FORMATTER_COMMENT_INDENT_ROOT_TAGS
As of 3.1, replaced byDefaultCodeFormatterConstants.FORMATTER_COMMENT_LINE_LENGTH
As of 3.1, replaced byDefaultCodeFormatterConstants.FORMATTER_COMMENT_INSERT_NEW_LINE_FOR_PARAMETER
As of 3.1, replaced byDefaultCodeFormatterConstants.FORMATTER_COMMENT_INSERT_EMPTY_LINE_BEFORE_ROOT_TAGS
as of 3.0, this hover is no longer availableSince 3.3. Not used anymore. Package view always restores with the last recently used setting.Since 3.3. Not used anymore. Type hierarchy view always restores with the last recently used setting.Use methodRefactoringCore.getConditionCheckingFailedSeverity()
.Use constantRefactoringStatus.ERROR
Use constantRefactoringStatus.FATAL
Use constantRefactoringStatus.INFO
Use constantRefactoringStatus.OK
Use constantRefactoringStatus.WARNING
since 3.1, useSpellingService.PREFERENCE_SPELLING_ENABLED
andSpellingService.PREFERENCE_SPELLING_ENGINE
Since 3.0, views now always update while editingSince 3.0, views now always update while editingSince 3.0, views now always update while editinguse UPDATE_REFERENCES or UPDATE_TEXTUAL_MATCHES or both.use UPDATE_TEXTUAL_MATCHESuse UPDATE_TEXTUAL_MATCHESreplaced as of 3.2 by an equivalent semantic highlighting, seeSemanticHighlightings.ANNOTATION
replaced as of 3.1 by an equivalent semantic highlighting, seeSemanticHighlightings.METHOD
no longer used, replaced byJAVA_KEYWORD
As of 3.0, replaced byAbstractDecoratedTextEditorPreferenceConstants.EDITOR_TAB_WIDTH
as of 3.1 useDefaultCodeFormatterConstants.FORMATTER_TAB_CHAR
-
MethodDescriptionThis method is missing crucial information necessary for proper wildcard binding key creation.JLS3 has been deprecated. This method has been replaced by
ReconcileContext.getAST4()
which returns an AST with JLS4 level.JLS4 has been deprecated. This method has been replaced byReconcileContext.getAST8()
which returns an AST with JLS8 level.JLS8 has been deprecated. This method has been replaced byReconcileContext.getAST(int)
which returns an AST with the given level.In the JLS8 API, the recursive structure is not valid.In the JLS8 API, the recursive structure is not valid.Use org.eclipse.jdt.core.dom.AST.convertCompilationUnit(int, CompilationUnitDeclaration, Map, boolean, CompilationUnit, int, IProgressMonitor) insteadClients should port their code to use the latest JLS* AST API and callAST.newAST(AST.JLS12, false)
instead of using this constructor.UseASTParser
instead.UseASTParser
instead.UseASTParser
instead.UseASTParser
instead.In the JLS3 API, this method is replaced byBodyDeclaration.modifiers()
, which contains a list ofModifier
nodes.In the JLS3 API, this method is replaced byClassInstanceCreation.getType()
, which returns aType
instead of aName
.In the JLS3 API, this method is replaced byClassInstanceCreation.setType(Type)
, which expects aType
instead of aName
.Use getLineNumber(int) instead. Be careful to handle the negative values.UseITypeBinding.getModifiers()
instead. This method was never implemented properly and historically has simply delegated to the methodgetModifiers
. Clients should callgetModifiers
method directly.The comment string was replaced in the 3.0 release by a representation of the structure of the doc comment. Seetags
.The comment string was replaced in the 3.0 release by a representation of the structure of the doc comment. Seetags
.UseMessage.getStartPosition()
instead.In the JLS3 API, this method is replaced byMethodDeclaration.getReturnType2()
, which may returnnull
.In the JLS8 API, this method is replaced byMethodDeclaration.extraDimensions()
which contains a list ofDimension
nodes.In the JLS3 API, this method is replaced byMethodDeclaration.setReturnType2(Type)
, which acceptsnull
.In the JLS8 API, this method is replaced byMethodDeclaration.thrownExceptionTypes()
.In the JLS3 API, this method is replaced bySingleVariableDeclaration.modifiers()
which contains a list of aModifier
nodes.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.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.use expressions() (see JLS 12)see JLS 12In the JLS3 API, this method is replaced byTypeDeclaration.getSuperclassType()
, which returns aType
instead of aName
.In the JLS3 API, this method is replaced byTypeDeclaration.setSuperclassType(Type)
, which expects aType
instead of aName
.In the JLS3 API, this method is replaced byTypeDeclaration.superInterfaceTypes()
.In the JLS3 API, this method is replaced byTypeDeclarationStatement.getDeclaration()
, which returnsAbstractTypeDeclaration
instead ofTypeDeclaration
.In the JLS3 API, this method is replaced byTypeDeclarationStatement.setDeclaration(AbstractTypeDeclaration)
which takesAbstractTypeDeclaration
instead ofTypeDeclaration
.In JLS8 and later, useVariableDeclaration.getExtraDimensions2Property()
instead.In the JLS8 API, this method is replaced byVariableDeclaration.extraDimensions()
which contains a list ofDimension
nodes.In the JLS3 API, this method is replaced byVariableDeclarationExpression.modifiers()
which contains a list of aModifier
nodes.In the JLS3 API, this method is replaced byVariableDeclarationStatement.modifiers()
which contains a list of aModifier
nodes.- use codeComplete(String, int, ICompletionRequestor) insteadUseITypeRoot.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).should only be used asIOrdinaryClassFile.getType()
.UseICodeAssist.codeComplete(int, ICompletionRequestor)
instead.UseICodeAssist.codeComplete(int, CompletionRequestor)
instead.UseICompilationUnit.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).UseITypeRoot.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).UseCompletionRequestor.accept(CompletionProposal)
instead.UseCompletionRequestor.accept(CompletionProposal)
instead.UseCompletionRequestor.completionFailure(IProblem)
instead.UseCompletionRequestor.accept(CompletionProposal)
instead.UseCompletionRequestor.accept(CompletionProposal)
instead.UseCompletionRequestor.accept(CompletionProposal)
instead.UseCompletionRequestor.accept(CompletionProposal)
instead.UseCompletionRequestor.accept(CompletionProposal)
instead.UseCompletionRequestor.accept(CompletionProposal)
instead.UseCompletionRequestor.accept(CompletionProposal)
instead.UseCompletionRequestor.accept(CompletionProposal)
instead.UseCompletionRequestor.accept(CompletionProposal)
instead.UseCompletionRequestor.accept(CompletionProposal)
instead.UseCompletionRequestor.accept(CompletionProposal)
instead.UseIStatus.getMessage()
insteadUseIMethod.getTypeParameters()
insteadClients are advised to specifically use eitherIPackageFragment.getOrdinaryClassFiles()
orIPackageFragment.getAllClassFiles()
to express their intent.UseICompilationUnit.discardWorkingCopy()
instead.UseICompilationUnit.findElements(IJavaElement)
instead.UseITypeRoot.findPrimaryType()
instead.UseICompilationUnit.findWorkingCopy(WorkingCopyOwner)
instead.UseIJavaElement.getPrimaryElement()
instead.UseIJavaElement.getPrimaryElement()
instead.UseICompilationUnit.getWorkingCopy(IProgressMonitor)
instead.UseICompilationUnit.hasResourceChanged()
instead.UseICompilationUnit.isWorkingCopy()
instead.UseICompilationUnit.restore()
instead.Overlapping roots are allowed in 2.1use addPreProcessingResourceChangedListener(listener, IResourceChangeEvent.POST_CHANGE) insteadUseJavaCore.getWorkingCopies(WorkingCopyOwner)
insteadUseNamingConventions.getBaseName(int, String, IJavaProject)
instead withNamingConventions.VK_PARAMETER
as variable kind.UseNamingConventions.getBaseName(int, String, IJavaProject)
instead withNamingConventions.VK_PARAMETER
as variable kind.UseNamingConventions.getBaseName(int, String, IJavaProject)
instead withNamingConventions.VK_INSTANCE_FIELD
orNamingConventions.VK_STATIC_FIELD
as variable kind.UseNamingConventions.getBaseName(int, String, IJavaProject)
instead withNamingConventions.VK_INSTANCE_FIELD
orNamingConventions.VK_STATIC_FIELD
as variable kind.UseNamingConventions.getBaseName(int, String, IJavaProject)
instead withNamingConventions.VK_LOCAL
as variable kind.UseNamingConventions.getBaseName(int, String, IJavaProject)
instead withNamingConventions.VK_LOCAL
as variable kind.UseNamingConventions.suggestVariableNames(int, int, String, IJavaProject, int, String[], boolean)
instead withNamingConventions.VK_PARAMETER
as variable kind.UseNamingConventions.suggestVariableNames(int, int, String, IJavaProject, int, String[], boolean)
instead withNamingConventions.VK_PARAMETER
as variable kind.UseNamingConventions.suggestVariableNames(int, int, String, IJavaProject, int, String[], boolean)
instead withNamingConventions.VK_LOCAL
as variable kind.UseNamingConventions.suggestVariableNames(int, int, String, IJavaProject, int, String[], boolean)
instead withNamingConventions.VK_LOCAL
as variable kind.this provisional API has been promoted toIModuleDescription.getRequiredModuleNames()
please useIModuleDescription.isSystemModule()
Replaced bySearchRequestor.beginReporting()
.Replaced bySearchRequestor.acceptSearchMatch(SearchMatch)
.Replaced bySearchRequestor.endReporting()
.UseSearchEngine.createJavaSearchScope(IJavaElement[])
with the package fragment roots that correspond to the binaries instead.UseSearchEngine.createJavaSearchScope(IJavaElement[])
with a Java project instead.UseSearchEngine.createJavaSearchScope(IJavaElement[])
with the package fragment roots that correspond to the binaries instead.UseSearchEngine.createJavaSearchScope(IJavaElement[])
with a Java project instead.UseSearchEngine.createJavaSearchScope(IJavaElement[])
instead.UseSearchPattern.createPattern(String, int, int, int)
instead.UseSearchPattern.createPattern(IJavaElement, int)
instead.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...The extension point has been deprecated, useToolFactory.createCodeFormatter(Map)
instead.UseToolFactory.createCodeFormatter(Map)
instead but note the different optionsThis has been replaced withIBytecodeVisitor._invokedynamic(int, int, IConstantPoolEntry)
Clients should port their code to use the new JLS3 AST API and callCompilationUnitSorter.sort(AST.JLS3, compilationUnit, positions, comparator, options, monitor)
instead of using this method.This has been replaced withIBytecodeVisitor._invokedynamic(int, int, IConstantPoolEntry)
UseWorkingCopyOwner.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.Use getExclusionFilters() or getInclusionFilters()Exception breakpoints can have a mixed set of filters and this method is maintained strictly for API backwards compatibilityException breakpoints can have a mixed set of filters. Use setInclusiveFilters(String[] filters) or setExclusiveFilters(String[] filters)UsegetReferenceType()
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 aDebugException
when a stack frame's method is contained in an interface.since 3.1, IJavaStackFrame extends org.eclipse.debug.core.IDropToFrame which defines canDropToFrame(). Use this method instead.usecreateStratumBreakpoint
insteadthePreferences
class has been deprecated, use theIEclipsePreferences
accessors insteadthePreferences
class has been deprecated, use theIEclipsePreferences
accessors insteaduse getErrorMessages()use getErrorMessages()As of 3.3, replaced byJUnitCore.addTestRunListener(TestRunListener)
As of 3.3, replaced byJUnitCore.removeTestRunListener(TestRunListener)
The call togetClasspath(ILaunchConfiguration)
inlaunch(...)
has been replaced with the call togetClasspathAndModulepath(ILaunchConfiguration)
.useNewTestCaseWizardPageOne.getJUnitVersion()
insteadUse setJUnit4or5 insteadorg.eclipse.jdt.launching.AbstractJavaLaunchConfigurationDelegate.getClasspath(ILaunchConfiguration) use getClasspathAndModulepathif possible, clients should use setVMArgs(String) onIVMInstall2
when possibleUsefindFreePort()
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.As of 3.5, this method is no longer calleduse getInputElement insteaduse setInputElement insteadUseJarPackageData.createJarWriter3(Shell)
insteaduseJarPackageData.createPlainJarBuilder()
insteadwill be removed in final 2.0will be removed in final 2.0will be removed in final 2.0will be removed in final 2.0As of 3.2, replaced byJavadocContentAccess.getHTMLContentReader(IMember, boolean, boolean)
The method is not intended to be used by clients.Bug 22518. Method never used: does not override ViewerSorter#isSorterProperty(Object, String). Method could be removed, but kept for API compatibility.IBufferFactory
has been replaced byWorkingCopyOwner
. The Java UI plug-in uses the primary working copy owner that can be accessed withnull
in API's that require an ownerJavadoc is now attached to the classpath entry. UseJavaUI.getJavadocBaseLocation(IJavaElement)
with the archive'sIPackageFragmentRoot
or useJavaUI.getLibraryJavadocLocation(IClasspathEntry)
with the archive'sIClasspathEntry
.UseJavaCore.getWorkingCopies(org.eclipse.jdt.core.WorkingCopyOwner)
instead withnull
as argument for owner.UseJavaCore.getWorkingCopies(org.eclipse.jdt.core.WorkingCopyOwner)
instead and filter the list withIJavaProject.isOnClasspath(IJavaElement)
.userevealInEditor(IEditorPart, IJavaElement)
insteadJavadoc is now attached to the classpath entry. Evaluate the libraries classpath entry and reconfigure the Javadoc location there.Javadoc is now attached to the classpath entry. Evaluate the libraries classpath entry and reconfigure the Javadoc location there.Not used anymore. This method is not accurate for methods in generic types.Since 3.0 compilation unit children are always provided as working copies. The Java model does not support the 'original' mode anymore.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.As of 3.0As of 3.0, no replacementAs of 3.0, replaced byJavaSourceViewerConfiguration.affectsTextPresentation(PropertyChangeEvent)
As of 3.0, replaced byJavaSourceViewerConfiguration.getCodeScanner()
As of 3.0, replaced byJavaSourceViewerConfiguration.getJavaDocScanner()
As of 3.0, replaced byJavaSourceViewerConfiguration.getMultilineCommentScanner()
As of 3.0, replaced byTextUtilities.computePartitionManagingCategories(IDocument)
As of 3.0, replaced byJavaSourceViewerConfiguration.getSinglelineCommentScanner()
As of 3.0, replaced byJavaSourceViewerConfiguration.getStringScanner()
Instead of file templates, the new type code template specifies the stub for a compilation unit.Use getTemplate(String,ICompilationUnit,int)Use getTypeComment(ICompilationUnit, String)
-
ConstructorDescriptionClients should port their code to use the latest JLS* AST API and call
AST.newAST(AST.JLS12, false)
instead of using this constructor.merged intoRenameJavaElementDescriptor
UseSearchEngine(ICompilationUnit[])
instead.UseSelectionDispatchAction.setSpecialSelectionProvider(ISelectionProvider)
instead. This API will be removed after 3.2 M5.UseSelectionDispatchAction.setSpecialSelectionProvider(ISelectionProvider)
instead. This API will be removed after 3.2 M5.UseSelectionDispatchAction.setSpecialSelectionProvider(ISelectionProvider)
instead. This constructor will be removed after 3.2 M5.UseStandardJavaElementContentProvider(boolean)
instead. Since 3.0 compilation unit children are always provided as working copies. The Java Model does not support the 'original' mode anymore.As of 3.0, replaced byJavaSourceViewerConfiguration(IColorManager, IPreferenceStore, ITextEditor, String)