-
Interfaces Interface Description org.eclipse.ant.ui.launching.IAntLaunchConfigurationConstants org.eclipse.jdt.core.IBufferFactory UseWorkingCopyOwner
insteadorg.eclipse.jdt.core.ICodeCompletionRequestor UseCompletionRequestor
instead.org.eclipse.jdt.core.ICodeFormatter UseCodeFormatter
instead (note: options have changed)org.eclipse.jdt.core.ICompletionRequestor UseCompletionRequestor
instead.org.eclipse.jdt.core.IWorkingCopy UseICompilationUnit
insteadorg.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 classSearchRequestor
replaces this interface.org.eclipse.jdt.core.search.ISearchPattern Since 3.0, the classSearchPattern
replaces this interface.org.eclipse.jdt.core.search.ITypeNameRequestor Use abstract classTypeNameRequestor
instead.org.eclipse.jdt.core.util.IClassFileDisassembler UseClassFileBytesDisassembler
insteadorg.eclipse.jdt.debug.core.IJavaPatternBreakpoint useIJavaStratumLineBreakpoint
insteadorg.eclipse.jdt.junit.ITestRunListener As of 3.3, replaced byTestRunListener
org.eclipse.jdt.launching.IRuntimeContainerComparator 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
.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
andorg.eclipse.debug.core.sourcelookup.containers
. This interface has been replaced byorg.eclipse.debug.core.sourcelookup.ISourceContainer
.org.eclipse.jdt.ui.text.java.IJavadocCompletionProcessor As of 3.2, replaced byorg.eclipse.jdt.ui.javaCompletionProposalComputer
extension-point.
-
Classes Class Description org.eclipse.jdt.core.CompletionRequestorAdapter SubclassCompletionRequestor
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 intoRenameJavaElementDescriptor
org.eclipse.jdt.core.refactoring.descriptors.RenameResourceDescriptor since 1.2, useRenameResourceDescriptor
fromorg.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
andorg.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
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.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
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
.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
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
.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
andorg.eclipse.debug.core.sourcelookup.containers
. This class has been replaced byorg.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
andorg.eclipse.debug.core.sourcelookup.containers
. This class has been replaced byorg.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
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.org.eclipse.jdt.launching.sourcelookup.LocalFileStorage In 3.0 this class is now provided by the debug platform. Clients should use the replacement classorg.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
andorg.eclipse.debug.core.sourcelookup.containers
. This class has been replaced byorg.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 classorg.eclipse.debug.core.sourcelookup.containers.ZipEntryStorage
.org.eclipse.jdt.ui.actions.FindStringsToExternalizeAction useExternalizeStringsAction
insteadorg.eclipse.jdt.ui.actions.OpenExternalJavadocAction As of 3.6, replaced byOpenAttachedJavadocAction
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 SeeCodeGeneration
org.eclipse.jdt.ui.jarpackager.JarWriter useJarWriter3
instead.org.eclipse.jdt.ui.jarpackager.JarWriter2 UseJarWriter3
instead which leverages newEFS
supportorg.eclipse.jdt.ui.JavaElementContentProvider use the StandardJavaElementContentProvider insteadorg.eclipse.jdt.ui.JavaElementSorter useJavaElementComparator
instead.org.eclipse.jdt.ui.SharedASTProvider UseSharedASTProviderCore
instead.org.eclipse.jdt.ui.wizards.NewJavaProjectWizardPage
-
Exceptions Exceptions Description 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.