| Interface and Description |
|---|
| 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. |
| 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.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:
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. |
| Field and Description |
|---|
| org.eclipse.jdt.launching.JavaRuntime.ATTR_CMDLINE
- use
IProcess.ATTR_CMDLINE |
| 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 |
| Method and Description |
|---|
| 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.launching.IVMInstall.setVMArguments(String[])
if possible, clients should use setVMArgs(String) on
IVMInstall2 when possible |