Interface and Description |
---|
org.eclipse.jdt.core.IBufferFactory
Use
WorkingCopyOwner instead |
org.eclipse.jdt.core.util.IClassFileDisassembler
- should use ClassFileBytesDisassembler instead
|
org.eclipse.jdt.core.ICodeCompletionRequestor
Use
CompletionRequestor instead. |
org.eclipse.jdt.core.ICodeFormatter
- should use org.eclipse.jdt.core.formatter.CodeFormatter instead (note: options have changed)
|
org.eclipse.jdt.core.ICompletionRequestor
Use
CompletionRequestor 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.ui.text.java.IJavadocCompletionProcessor
As of 3.2, replaced by
org.eclipse.jdt.ui.javaCompletionProposalComputer extension-point. |
org.eclipse.jdt.debug.core.IJavaPatternBreakpoint
use
IJavaStratumLineBreakpoint instead |
org.eclipse.jdt.core.search.IJavaSearchResultCollector
Since 3.0, the class
SearchRequestor replaces this interface. |
org.eclipse.jdt.launching.sourcelookup.IJavaSourceLocation
In 3.0, the debug platform provides source lookup facilities that
should be used in place of the Java source lookup support provided in 2.0.
The new facilities provide a source lookup director that coordinates source
lookup among a set of participants, searching a set of source containers.
See the following packages:
org.eclipse.debug.core.sourcelookup
and org.eclipse.debug.core.sourcelookup.containers . This interface
has been replaced by
org.eclipse.debug.core.sourcelookup.ISourceContainer . |
org.eclipse.jdt.launching.IRuntimeContainerComparator
support has been added to
ClasspathContainerInitializer
to handle comparison of classpath containers. Use
ClasspathContainerInitializer.getComparisonID(IPath,IJavaProject) .
When a classpath container implements this interface, this interface is
used to determine equality before using the support defined in
ClasspathContainerInitializer . |
org.eclipse.jdt.core.search.ISearchPattern
Since 3.0, the class
SearchPattern replaces this interface. |
org.eclipse.jdt.core.search.ITypeNameRequestor
Use abstract class
TypeNameRequestor instead. |
org.eclipse.jdt.core.IWorkingCopy
Use
ICompilationUnit instead |
Class and Description |
---|
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.core.CompletionRequestorAdapter
Subclass
CompletionRequestor instead. |
org.eclipse.jdt.launching.sourcelookup.DirectorySourceLocation
In 3.0, the debug platform provides source lookup facilities that
should be used in place of the Java source lookup support provided in 2.0.
The new facilities provide a source lookup director that coordinates source
lookup among a set of participants, searching a set of source containers.
See the following packages:
org.eclipse.debug.core.sourcelookup
and org.eclipse.debug.core.sourcelookup.containers . This class
has been replaced by
org.eclipse.debug.core.sourcelookup.containers.DirectorySourceContainer . |
org.eclipse.jdt.core.jdom.DOMFactory
The JDOM was made obsolete by the addition in 2.0 of the more
powerful, fine-grained DOM/AST API found in the
org.eclipse.jdt.core.dom package.
|
org.eclipse.jdt.ui.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.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:
ATTR_SOURCE_PATH_PROVIDER
attribute (if present), or a default source lookup path based on a configuration's
runtime classpath. This class has been replaced by the Java source lookup
director which is an internal class, but can be used via the
sourceLocatorId attribute on a launch configuration type extension. |
org.eclipse.jdt.debug.ui.JavaSourceLookupDialog
In 3.0, the debug platform provides source lookup facilities that
should be used in place of the Java source lookup support provided in 2.0.
The new facilities provide a source lookup director that coordinates source
lookup among a set of participants, searching a set of source containers.
See the following packages:
org.eclipse.debug.core.sourcelookup
and org.eclipse.debug.core.sourcelookup.containers . This class
has been replaced by a dialog in the debug platform -
org.eclipse.debug.ui.sourcelookup.SourceLookupDialog . |
org.eclipse.jdt.debug.ui.launchConfigurations.JavaSourceLookupTab
In 3.0, the debug platform provides source lookup facilities that
should be used in place of the Java source lookup support provided in 2.0.
The new facilities provide a source lookup director that coordinates source
lookup among a set of participants, searching a set of source containers.
See the following packages:
org.eclipse.debug.core.sourcelookup
and org.eclipse.debug.core.sourcelookup.containers . This class
has been replaced by a source lookup tab in the debug platform -
org.eclipse.debug.ui.sourcelookup.SourceLookupTab . |
org.eclipse.jdt.debug.ui.JavaUISourceLocator
In 3.0, the debug platform provides source lookup facilities that
should be used in place of the Java source lookup support provided in 2.0.
The new facilities provide a source lookup director that coordinates source
lookup among a set of participants, searching a set of source containers.
See the following packages:
org.eclipse.debug.core.sourcelookup
and org.eclipse.debug.core.sourcelookup.containers . This class
has been replaced by a Java source lookup director and Java source lookup
participant. To migrate to the new source lookup support clients should
add two new attributes to their launch configuration type extensions:
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 . |
Exceptions and 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.
|
Copyright (c) IBM Corp. and others 2000, 2006. All Rights Reserved.