Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDarin Wright2002-02-27 15:34:54 -0500
committerDarin Wright2002-02-27 15:34:54 -0500
commit8fa8f52621a7df049d142632d01aea38207109cb (patch)
tree589dfc3846a45874dc198aff44834657cd18b3a3
parent3e8457b28500bb7dcdbc33754f64762e9fcb1c4c (diff)
downloadeclipse.platform.debug-8fa8f52621a7df049d142632d01aea38207109cb.tar.gz
eclipse.platform.debug-8fa8f52621a7df049d142632d01aea38207109cb.tar.xz
eclipse.platform.debug-8fa8f52621a7df049d142632d01aea38207109cb.zip
bug 6485 (in progress)
-rw-r--r--org.eclipse.debug.core/core/org/eclipse/debug/core/IBreakpointManager.java5
-rw-r--r--org.eclipse.debug.core/core/org/eclipse/debug/core/model/package.html12
-rw-r--r--org.eclipse.debug.core/core/org/eclipse/debug/core/package.html11
-rw-r--r--org.eclipse.debug.core/doc/org_eclipse_debug_core.html8
-rw-r--r--org.eclipse.debug.core/doc/org_eclipse_debug_core_launch_configuration_types.html2
5 files changed, 20 insertions, 18 deletions
diff --git a/org.eclipse.debug.core/core/org/eclipse/debug/core/IBreakpointManager.java b/org.eclipse.debug.core/core/org/eclipse/debug/core/IBreakpointManager.java
index c10b34d73..9b6514520 100644
--- a/org.eclipse.debug.core/core/org/eclipse/debug/core/IBreakpointManager.java
+++ b/org.eclipse.debug.core/core/org/eclipse/debug/core/IBreakpointManager.java
@@ -86,8 +86,9 @@ public interface IBreakpointManager {
public boolean isRegistered(IBreakpoint breakpoint);
/**
- * Notifies all registered listeners that this breakpoint has changed.
- * Has no effect if the given breakpoint is not currently registered.
+ * Notifies all registered listeners that the given
+ * breakpoint has changed. Has no effect if the given
+ * breakpoint is not currently registered.
*
* This method is intended to be used when a breakpoint
* attribute is changed that does not alter the breakpoint's
diff --git a/org.eclipse.debug.core/core/org/eclipse/debug/core/model/package.html b/org.eclipse.debug.core/core/org/eclipse/debug/core/model/package.html
index 951d97dcc..3f9882d9c 100644
--- a/org.eclipse.debug.core/core/org/eclipse/debug/core/model/package.html
+++ b/org.eclipse.debug.core/core/org/eclipse/debug/core/model/package.html
@@ -3,7 +3,7 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Debug Tools [org.eclipse.debug.core.model]</title>
+<title>Eclipse Debug Platform [org.eclipse.debug.core.model]</title>
</head>
<body bgcolor="#FFFFFF">
@@ -18,7 +18,7 @@ representing common artifacts in debuggable programs. The debug plug-in itself d
any implementations of a debug model. It is intended that third parties providing an integrated
set of development tools for a specific language will also implement a debug model for that language,
using an underlying debug architecture of their choice. For example, Java Tooling provides an
-implementation of a debug model based on the standard Java Debug Interface (JDI).</p>
+implementation of a debug model based on the standard Java Platform Debug Architecture (JPDA).</p>
<h4>The Debug Model</h4>
@@ -56,14 +56,14 @@ termination of a thread.</p>
<p>Breakpoints are used to suspend the execution of a program being debugged. There are
many kinds of breakpoints - line breakpoints, conditional line breakpoints, hit count
breakpoints, exception breakpoints, etc. The kinds of breakpoints supported by each debug
-architecture (for example, JDI), and the information required to create those breakpoints
-is dictated by each debug architecture. Eclipse Debug Tools supports an extensible
+architecture, and the information required to create those breakpoints
+is dictated by each debug architecture. The debug platform supports an extensible
set of breakpoint via the breakpoints extension point.</p>
-<p>Eclipse Debug Tools provides a breakpoint manager that maintains the collection of all
+<p>The debug platform provides a breakpoint manager that maintains the collection of all
registered breakpoints. Clients add and remove breakpoints via this manager. Breakpoints are
implemented by instances of IBreakpoint. Each breakpoint object has an associated marker,
-which provides persistence and presentation in editors. Eclipse Debug Tools defines a generic
+which provides persistence and presentation in editors. The debug platform defines a generic
breakpoint and line breakpoint, as well as their corresponding marker definitions. Breakpoint
creation is a client responsibility - that is, defining the attributes of a breakpoint and
the resource to associate a breakpoin marker with.</p>
diff --git a/org.eclipse.debug.core/core/org/eclipse/debug/core/package.html b/org.eclipse.debug.core/core/org/eclipse/debug/core/package.html
index 45d261dbf..c8e7d76ca 100644
--- a/org.eclipse.debug.core/core/org/eclipse/debug/core/package.html
+++ b/org.eclipse.debug.core/core/org/eclipse/debug/core/package.html
@@ -3,7 +3,7 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Debug Tools</title>
+<title>Eclipse Debug Platform</title>
</head>
<body bgcolor="#FFFFFF">
@@ -23,11 +23,11 @@ The debug plug-in itself does not provide any implementations of a debug model.
intended that third parties providing an integrated set of development tools for a
specific language will also implement a debug model for that language, using an underlying
debug architecture of their choice. For example, Java Tooling provides an implementation
-of a debug model based on the standard Java Debug Interface (JDI).</p>
+of a debug model based on the standard Java Platform Debug Architecture (JPDA).</p>
<h4>The Managers</h4>
-<p>Eclipse Debug Tools defines and provides an implementation of the following managers:
+<p>The debug platform defines and provides an implementation of the following managers:
<ul>
<li>Launch Manager - The launch manager maintains the set of registered launches - that is,
a collection of programs that have been launched in debuggable or non-debuggable (run) mode.
@@ -55,8 +55,9 @@ of a debug model based on the standard Java Debug Interface (JDI).</p>
The actual launching of an application is performed
by an associated implementation of a launch configuration delegate, which is specifed by each launch configuration
type extension.</p>
-<p>A launch configuration may be shared in a repository via standard VCM mechanisms, or may
- be stored locally, essentially making the launch configuration private for a single user.</p>
+<p>A launch configuration may be stored as a file in the worksapce (and shared in a repository via
+ standard team mechanisms), or may be stored locally, essentially making the launch configuration
+ private for a single user.</p>
</body>
diff --git a/org.eclipse.debug.core/doc/org_eclipse_debug_core.html b/org.eclipse.debug.core/doc/org_eclipse_debug_core.html
index bce865f9e..a76f48144 100644
--- a/org.eclipse.debug.core/doc/org_eclipse_debug_core.html
+++ b/org.eclipse.debug.core/doc/org_eclipse_debug_core.html
@@ -8,14 +8,14 @@
<body link="#0000FF" vlink="#800080">
-<h1 align="center">Eclipse Debug Tools Infrastructure</h1>
+<h1 align="center">Eclipse Debug Platform</h1>
-<p>The debug tools infrastructure plug-in, <b>org.eclipse.debug.core</b>,
+<p>The debug platform plug-in, <b>org.eclipse.debug.core</b>,
defines a model for language independent debugging. A set of common debug artifacts and
actions are defined by interfaces, for which specific debug architectures may provide
implementations. For example, some common artifacts are threads, stack frames, and
variables; some common actions are terminate, suspend, step, and resume. A debug
-architecture, such as JDI (Java Debug Interface), can provide an implementation of the
+architecture, such as the Java Platform Debug Architecture (JPDA), can provide an implementation of the
artifacts and actions. The debug plug-in also provides a facilities to support
breakpoint management, expression management, and program launching.<br>
</p>
@@ -27,7 +27,7 @@ breakpoint management, expression management, and program launching.<br>
<p>The following extension points are used to support and extend the debug infrastructure:
<ul>
- <li><a href="org_eclipse_debug_core_launcher_configuration_types.html">org.eclipse.debug.core.launchConfigurationTypes</a></li>
+ <li><a href="org_eclipse_debug_core_launch_configuration_types.html">org.eclipse.debug.core.launchConfigurationTypes</a></li>
<li><a href="org_eclipse_debug_core_breakpoints.html">org.eclipse.debug.core.breakpoints</a></li>
</ul>
diff --git a/org.eclipse.debug.core/doc/org_eclipse_debug_core_launch_configuration_types.html b/org.eclipse.debug.core/doc/org_eclipse_debug_core_launch_configuration_types.html
index 06dfee83e..1e7e63e8d 100644
--- a/org.eclipse.debug.core/doc/org_eclipse_debug_core_launch_configuration_types.html
+++ b/org.eclipse.debug.core/doc/org_eclipse_debug_core_launch_configuration_types.html
@@ -36,7 +36,7 @@ responsible for the implementation of launching an application.</p>
instances of this type will delegate to instances of this class
to perform launching.</li>
<li><code>modes</code> specifies a comma separated list of the modes this
- type of launch configuration suports - <code>"run"</code> and/or <code>"debug</code>.</li>
+ type of launch configuration suports - <code>"run"</code> and/or <code>"debug"</code>.</li>
<li><code>name</code> specifies a human readable name for this type
of launch configuration.</li>
</ul>

Back to the top