Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlexander Kurtakov2019-02-14 10:33:35 -0500
committerAlexander Kurtakov2019-02-14 10:45:48 -0500
commit62a4a631630ed77cfdd1e27333cafae0a7cbcf27 (patch)
tree07093d13fc2718ae6d7b9ed1ca9a392449c8377c /org.eclipse.debug.ui/ui/org/eclipse/debug/ui
parent2341d0c7e25069e795fafd9d027acec7f99c8884 (diff)
downloadeclipse.platform.debug-62a4a631630ed77cfdd1e27333cafae0a7cbcf27.tar.gz
eclipse.platform.debug-62a4a631630ed77cfdd1e27333cafae0a7cbcf27.tar.xz
eclipse.platform.debug-62a4a631630ed77cfdd1e27333cafae0a7cbcf27.zip
Bug 543933 - Build javadocs with Java 11I20190215-0630I20190215-0055I20190214-1800
Fix javadoc warnings catched by Java 11 tool with XDoclint:html. Change-Id: I99061cad4e8a9e3eb18bfc97143fa893715a58f8 Signed-off-by: Alexander Kurtakov <akurtako@redhat.com>
Diffstat (limited to 'org.eclipse.debug.ui/ui/org/eclipse/debug/ui')
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IBreakpointOrganizerDelegate.java19
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IDebugModelPresentation.java73
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IDetailPaneFactory.java15
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IInstructionPointerPresentation.java49
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ILaunchConfigurationTabGroup.java73
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ILaunchGroup.java15
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ILaunchShortcut.java98
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ISourcePresentation.java41
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/BreakpointTypesContribution.java24
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/IAddMemoryRenderingsTarget.java21
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/ILaunchable.java58
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/IToggleBreakpointsTargetFactory.java17
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/IVariableValueEditor.java9
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerBreakpointTypesActionDelegate.java25
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerEnableDisableBreakpointActionDelegate.java1
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerRunToLineActionDelegate.java4
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerToggleBreakpointActionDelegate.java20
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RunAction.java1
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/console/IConsoleColorProvider.java15
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/memory/IMemoryRendering.java41
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/memory/IMemoryRenderingSynchronizationService.java10
-rw-r--r--org.eclipse.debug.ui/ui/org/eclipse/debug/ui/sourcelookup/ISourceContainerBrowser.java16
22 files changed, 353 insertions, 292 deletions
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IBreakpointOrganizerDelegate.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IBreakpointOrganizerDelegate.java
index 30b25297b..81679e6a5 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IBreakpointOrganizerDelegate.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IBreakpointOrganizerDelegate.java
@@ -19,16 +19,18 @@ import org.eclipse.debug.internal.ui.DebugUIPlugin;
import org.eclipse.jface.util.IPropertyChangeListener;
/**
- * A breakpoint organizer is used to categorize breakpoints and provides
- * change notification when categorization has changed. Categories are represented
- * as arbitrary adaptable objects. For example, projects could be used to
- * categorize breakpoints. Images and labels for categories are generated
- * via workbench adapters.
+ * A breakpoint organizer is used to categorize breakpoints and provides change
+ * notification when categorization has changed. Categories are represented as
+ * arbitrary adaptable objects. For example, projects could be used to
+ * categorize breakpoints. Images and labels for categories are generated via
+ * workbench adapters.
* <p>
* Organizers may optionally support breakpoint recategorization.
* </p>
* <p>
* Following is example plug-in XML for contributing a breakpoint organizer.
+ * </p>
+ *
* <pre>
* &lt;extension point="org.eclipse.debug.ui.breakpointOrganizers"&gt;
* &lt;breakpointOrganizer
@@ -38,6 +40,7 @@ import org.eclipse.jface.util.IPropertyChangeListener;
* icon="icons/full/obj16/example_org.png"/&gt;
* &lt;/extension&gt;
* </pre>
+ *
* The attributes are specified as follows:
* <ul>
* <li><code>class</code> Fully qualified name of a Java class that implements
@@ -48,11 +51,11 @@ import org.eclipse.jface.util.IPropertyChangeListener;
* <li><code>icon</code> Optional path to an icon which can be shown for this
* organizer</li>
* </ul>
- * </p>
* <p>
- * Clients contributing a breakpoint organizer are intended to implement
- * this interface.
+ * Clients contributing a breakpoint organizer are intended to implement this
+ * interface.
* </p>
+ *
* @since 3.1
*/
public interface IBreakpointOrganizerDelegate {
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IDebugModelPresentation.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IDebugModelPresentation.java
index d42da9e52..072cb2981 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IDebugModelPresentation.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IDebugModelPresentation.java
@@ -19,16 +19,18 @@ import org.eclipse.jface.viewers.ILabelProvider;
import org.eclipse.swt.graphics.Image;
/**
- * A debug model presentation is responsible for providing labels, images,
- * and editors associated with debug elements in a specific debug model.
- * Extensions of type <code>org.eclipse.debug.ui.debugModelPresentations</code> implement
+ * A debug model presentation is responsible for providing labels, images, and
+ * editors associated with debug elements in a specific debug model. Extensions
+ * of type <code>org.eclipse.debug.ui.debugModelPresentations</code> implement
* this interface. Generally, a debug model implementation will also provide a
- * debug model presentation extension to render and display its elements. A debug
- * model presentation is registered for a specific debug model, and is responsible
- * for the presentation elements defined/implemented by that model.
+ * debug model presentation extension to render and display its elements. A
+ * debug model presentation is registered for a specific debug model, and is
+ * responsible for the presentation elements defined/implemented by that model.
* <p>
* A debug model presentation extension is defined in <code>plugin.xml</code>.
* Following is an example definition of a debug model presentation extension.
+ * </p>
+ *
* <pre>
* &lt;extension point="org.eclipse.debug.ui.debugModelPresentations"&gt;
* &lt;debugModelPresentation
@@ -38,48 +40,53 @@ import org.eclipse.swt.graphics.Image;
* &lt;/debugModelPresentation&gt;
* &lt;/extension&gt;
* </pre>
+ *
* The attributes are specified as follows:
* <ul>
- * <li><code>id</code> specifies the identifier of the debug model this presentation
- * is responsible for. Corresponds to the model identifier returned from a debug
- * element - see <code>IDebugElement.getModelIndentifier</code></li>
+ * <li><code>id</code> specifies the identifier of the debug model this
+ * presentation is responsible for. Corresponds to the model identifier returned
+ * from a debug element - see
+ * <code>IDebugElement.getModelIndentifier</code></li>
* <li><code>class</code> specifies the fully qualified name of the Java class
- * that implements this interface.</li>
- * <li><code>detailsViewerConfiguration</code> optionally specifies the fully qualified name of the Java class
- * that is an instance of <code>org.eclipse.jface.text.source.SourceViewerConfiguration</code>.
- * When specified, the source viewer configuration will be used in the "details" area of the
- * variables and expressions view when displaying the details of an element from the
- * debug model associated with this debug model presentation. When unspecified,
- * a default configuration is used.</li>
+ * that implements this interface.</li>
+ * <li><code>detailsViewerConfiguration</code> optionally specifies the fully
+ * qualified name of the Java class that is an instance of
+ * <code>org.eclipse.jface.text.source.SourceViewerConfiguration</code>. When
+ * specified, the source viewer configuration will be used in the "details" area
+ * of the variables and expressions view when displaying the details of an
+ * element from the debug model associated with this debug model presentation.
+ * When unspecified, a default configuration is used.</li>
* </ul>
- * </p>
* <p>
- * To allow for an extensible configuration, this interface defines
- * a <code>setAttribute</code> method. The debug UI plug-in defines
- * one presentation attribute:
+ * To allow for an extensible configuration, this interface defines a
+ * <code>setAttribute</code> method. The debug UI plug-in defines one
+ * presentation attribute:
* <ul>
- * <li><code>DISPLAY_VARIABLE_TYPE_NAMES</code> - This is a boolean attribute
- * indicating whether variable elements should be rendered with the declared
- * type of a variable. For example, a Java debug model presentation would render
- * an integer as <code>"int x = 3"</code> when true, and <code>"x = 3"</code>
- * when false.</li>
+ * <li><code>DISPLAY_VARIABLE_TYPE_NAMES</code> - This is a boolean attribute
+ * indicating whether variable elements should be rendered with the declared
+ * type of a variable. For example, a Java debug model presentation would render
+ * an integer as <code>"int x = 3"</code> when true, and <code>"x = 3"</code>
+ * when false.</li>
* </ul>
- * </p>
+ *
* <p>
- * Clients may define new presentation attributes. For example, a client may wish
- * to define a "hexadecimal" property to display numeric values in hexadecimal. Implementations
- * should honor the presentation attributes defined by this interface where possible,
- * but do not need to honor presentation attributes defined by other clients.
- * To access the debug model presentation for a debug view, clients should use
+ * Clients may define new presentation attributes. For example, a client may
+ * wish to define a "hexadecimal" property to display numeric values in
+ * hexadecimal. Implementations should honor the presentation attributes defined
+ * by this interface where possible, but do not need to honor presentation
+ * attributes defined by other clients. To access the debug model presentation
+ * for a debug view, clients should use
* <code>IDebugView#getPresentation(String)</code>.
* </p>
* <p>
- * Since 3.1, debug model presentations may optionally implement <code>IColorProvider</code>
- * and <code>IFontProvider</code> to override default fonts and colors for debug elements.
+ * Since 3.1, debug model presentations may optionally implement
+ * <code>IColorProvider</code> and <code>IFontProvider</code> to override
+ * default fonts and colors for debug elements.
* </p>
* <p>
* Clients may implement this interface.
* </p>
+ *
* @see org.eclipse.debug.core.model.IDebugElement
* @see org.eclipse.jface.viewers.ILabelProvider
* @see org.eclipse.debug.ui.IDebugView
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IDetailPaneFactory.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IDetailPaneFactory.java
index 935690734..0d2ebf204 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IDetailPaneFactory.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IDetailPaneFactory.java
@@ -20,8 +20,11 @@ import org.eclipse.jface.viewers.IStructuredSelection;
/**
* A detail pane factory creates one or more types of detail panes.
* <p>
- * Detail pane factories are contributed via the <code>org.eclipse.debug.ui.detailPaneFactories</code>
- * extension point. Following is an example of a detail pane factory extension:
+ * Detail pane factories are contributed via the
+ * <code>org.eclipse.debug.ui.detailPaneFactories</code> extension point.
+ * Following is an example of a detail pane factory extension:
+ * </p>
+ *
* <pre>
* &lt;extension point="org.eclipse.debug.ui.detailPaneFactories"&gt;
* &lt;detailFactories
@@ -30,10 +33,10 @@ import org.eclipse.jface.viewers.IStructuredSelection;
* &lt;/detailFactories&gt;
* &lt;/extension&gt;
* </pre>
- * </p>
- * <p>
- * <p>
- * Clients contributing a detail pane factory are intended to implement this interface.
+ *
+ * Clients contributing a detail pane factory are intended to implement this
+ * interface.
+ *
* @see IDetailPane
* @since 3.3
*
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IInstructionPointerPresentation.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IInstructionPointerPresentation.java
index 0f1888d79..4db95a9ce 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IInstructionPointerPresentation.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/IInstructionPointerPresentation.java
@@ -19,42 +19,49 @@ import org.eclipse.swt.graphics.Image;
import org.eclipse.ui.IEditorPart;
/**
- * A debug model presentation may implement this interface to override
- * standard annotations used to display instruction pointers for stack frames.
+ * A debug model presentation may implement this interface to override standard
+ * annotations used to display instruction pointers for stack frames.
* <p>
* A client has several options when overriding default instruction pointer
- * annotations, and the debug platform uses the following prioritized order
- * when computing an annotation for a stack frame.
+ * annotations, and the debug platform uses the following prioritized order when
+ * computing an annotation for a stack frame.
+ * </p>
* <ol>
- * <li>Specify the annotation object to use. This is done by returning a non-<code>null</code>
- * value from <code>getInstructionPointerAnnotation(..)</code>.</li>
- * <li>Specify an <code>annotationType</code> extension to use.
- * This is done by returning a non-<code>null</code> value from
- * <code>getInstructionPointerAnnotationType(..)</code>. When specified, the annotation
- * type controls the image displayed via its associated
- * <code>markerAnnotationSpecification</code>.</li>
- * <li>Specify the image to use. This is done by returning a non-<code>null</code>
- * value from <code>getInstructionPointerImage(..)</code>.</li>
+ * <li>Specify the annotation object to use. This is done by returning a
+ * non-<code>null</code> value from
+ * <code>getInstructionPointerAnnotation(..)</code>.</li>
+ * <li>Specify an <code>annotationType</code> extension to use. This is done by
+ * returning a non-<code>null</code> value from
+ * <code>getInstructionPointerAnnotationType(..)</code>. When specified, the
+ * annotation type controls the image displayed via its associated
+ * <code>markerAnnotationSpecification</code>.</li>
+ * <li>Specify the image to use. This is done by returning a
+ * non-<code>null</code> value from
+ * <code>getInstructionPointerImage(..)</code>.</li>
* </ol>
- * Additionally, when specifying an annotation type or image the text
- * for the instruction pointer may be specified by returning a non-<code>null</code>
+ * <p>
+ * Additionally, when specifying an annotation type or image the text for the
+ * instruction pointer may be specified by returning a non-<code>null</code>
* value from <code>getInstructionPointerText(..)</code>.
* </p>
* <p>
* These methods are called when the debugger has opened an editor to display
- * source for the given stack frame. The image will be positioned based on stack frame
- * line number and character ranges.
+ * source for the given stack frame. The image will be positioned based on stack
+ * frame line number and character ranges.
* </p>
* <p>
* By default, the debug platform uses different annotations for top stack
* frames and non-top stack frames in a thread. The default platform annotations
- * are contributed as <code>annotationType</code> extensions with
- * the identifiers <code>IDebugUIConstants.ANNOTATION_INSTRUCTION_POINTER_CURRENT</code>
- * and <code>IDebugUIConstants.ANNOTAION_INSTRUCTION_POINTER_SECONDARY</code>.
+ * are contributed as <code>annotationType</code> extensions with the
+ * identifiers
+ * <code>IDebugUIConstants.ANNOTATION_INSTRUCTION_POINTER_CURRENT</code> and
+ * <code>IDebugUIConstants.ANNOTAION_INSTRUCTION_POINTER_SECONDARY</code>.
* </p>
* <p>
- * Clients implementing a debug model presentation may also implement this interface.
+ * Clients implementing a debug model presentation may also implement this
+ * interface.
* </p>
+ *
* @since 3.2
*/
public interface IInstructionPointerPresentation extends IDebugModelPresentation {
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ILaunchConfigurationTabGroup.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ILaunchConfigurationTabGroup.java
index 7deb97411..1de9f4bbf 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ILaunchConfigurationTabGroup.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ILaunchConfigurationTabGroup.java
@@ -19,44 +19,46 @@ import org.eclipse.debug.core.ILaunchConfiguration;
import org.eclipse.debug.core.ILaunchConfigurationWorkingCopy;
/**
- * A launch configuration tab group is used to edit/view attributes
- * of a specific type of launch configuration. Launch
- * configurations are presented in a dialog, with a tab folder.
- * Each tab manipulates one or more attributes of a launch
- * configuration. The tab group controls which tabs are
- * displayed for a specific type of launch configuration,
- * and provides a mechanism for overriding configuration
- * initialization performed by tabs.
+ * A launch configuration tab group is used to edit/view attributes of a
+ * specific type of launch configuration. Launch configurations are presented in
+ * a dialog, with a tab folder. Each tab manipulates one or more attributes of a
+ * launch configuration. The tab group controls which tabs are displayed for a
+ * specific type of launch configuration, and provides a mechanism for
+ * overriding configuration initialization performed by tabs.
* <p>
* A tab group has the following lifecycle methods:
+ * </p>
* <ul>
- * <li><code>createTabs(ILaunchConfigurationDialog, String)</code> -
- * this is the first method called on a tab group after it is instantiated.</li>
- * <li><code>initializeFrom(ILaunchConfiguration)</code> - called when a
- * launch configuration is selected to be displayed.</li>
+ * <li><code>createTabs(ILaunchConfigurationDialog, String)</code> - this is the
+ * first method called on a tab group after it is instantiated.</li>
+ * <li><code>initializeFrom(ILaunchConfiguration)</code> - called when a launch
+ * configuration is selected to be displayed.</li>
* <li><code>performApply(ILaunchConfigurationWorkingCopy)</code> - called when
- * a tab group's values are to be written to a launch configuration.</li>
- * <li><code>dispose()</code> - the last method called on a tab group, when it is
- * to perform any required cleanup. Note that a tab can be disposed before its control
- * has been created.</li>
+ * a tab group's values are to be written to a launch configuration.</li>
+ * <li><code>dispose()</code> - the last method called on a tab group, when it
+ * is to perform any required cleanup. Note that a tab can be disposed before
+ * its control has been created.</li>
* </ul>
- * The method <code>setDefaults(ILaunchConfigurationWorkingCopy)</code>
- * can be called before a tab's controls are created.
+ * <p>
+ * The method <code>setDefaults(ILaunchConfigurationWorkingCopy)</code> can be
+ * called before a tab's controls are created.
* </p>
* <p>
* The launch tab framework was originally designed to handle inter tab
- * communication by applying attributes from the active tab to a launch configuration
- * being edited, when a tab is exited, and by initializing a tab when activated.
- * In 3.0, the addition of the methods <code>activated</code> and <code>deactivated</code>
- * allow tabs to determine the appropriate course of action. The default implementation
- * in <code>AbstractLaunchConfigurationTab</code> is to call the old methods
- * (<code>initializeFrom</code> and <code>performApply</code>). Tabs should override
- * the new methods as required.
+ * communication by applying attributes from the active tab to a launch
+ * configuration being edited, when a tab is exited, and by initializing a tab
+ * when activated. In 3.0, the addition of the methods <code>activated</code>
+ * and <code>deactivated</code> allow tabs to determine the appropriate course
+ * of action. The default implementation in
+ * <code>AbstractLaunchConfigurationTab</code> is to call the old methods
+ * (<code>initializeFrom</code> and <code>performApply</code>). Tabs should
+ * override the new methods as required.
* </p>
* <p>
* A launch configuration group extension is defined in <code>plugin.xml</code>.
- * Following is an example definition of a launch configuration
- * group extension.
+ * Following is an example definition of a launch configuration group extension.
+ * </p>
+ *
* <pre>
* &lt;extension point="org.eclipse.debug.ui.launchConfigurationTabGroups"&gt;
* &lt;launchConfigurationTabGroup
@@ -66,20 +68,21 @@ import org.eclipse.debug.core.ILaunchConfigurationWorkingCopy;
* &lt;/launchConfigurationTabGroup&gt;
* &lt;/extension&gt;
* </pre>
+ *
* The attributes are specified as follows:
* <ul>
- * <li><code>id</code> specifies a unique identifier for this launch configuration
- * tab group.</li>
- * <li><code>type</code> specifies launch configuration type that this tab
- * group is applicable to (corresponds to the id of a launch configuration type
- * extension).</li>
- * <li><code>class</code> specifies a fully qualified name of a Java class
- * that implements <code>ILaunchConfigurationTabGroup</code>.</li>
+ * <li><code>id</code> specifies a unique identifier for this launch
+ * configuration tab group.</li>
+ * <li><code>type</code> specifies launch configuration type that this tab group
+ * is applicable to (corresponds to the id of a launch configuration type
+ * extension).</li>
+ * <li><code>class</code> specifies a fully qualified name of a Java class that
+ * implements <code>ILaunchConfigurationTabGroup</code>.</li>
* </ul>
- * </p>
* <p>
* This interface is intended to be implemented by clients.
* </p>
+ *
* @see org.eclipse.debug.core.ILaunchConfigurationType
* @see org.eclipse.debug.core.ILaunchConfiguration
* @see org.eclipse.debug.ui.ILaunchConfigurationTab
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ILaunchGroup.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ILaunchGroup.java
index 9dc2d4ef1..ca208a779 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ILaunchGroup.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ILaunchGroup.java
@@ -16,13 +16,14 @@ package org.eclipse.debug.ui;
import org.eclipse.jface.resource.ImageDescriptor;
/**
- * A launch group identifies a group of launch configurations by a launch
- * mode and category. The launch configuration dialog can be opened on
- * a launch group, and a launch history is maintained for each group.
- * A launch group is defined in plug-in XML via the <code>launchGroups</code>
- * extension point.
+ * A launch group identifies a group of launch configurations by a launch mode
+ * and category. The launch configuration dialog can be opened on a launch
+ * group, and a launch history is maintained for each group. A launch group is
+ * defined in plug-in XML via the <code>launchGroups</code> extension point.
* <p>
* Following is an example of a launch group contribution:
+ * </p>
+ *
* <pre>
* &lt;extension point="org.eclipse.debug.ui.launchGroups"&gt;
* &lt;launchGroup
@@ -33,16 +34,16 @@ import org.eclipse.jface.resource.ImageDescriptor;
* &lt;/launchGroup&gt;
* &lt;/extension&gt;
* </pre>
- * </p>
* <p>
* The debug platform defines constants for the identifiers of the launch groups
* provided by the debug platform:
+ * </p>
* <ul>
* <li>IDebugUIConstants.ID_DEBUG_LAUNCH_GROUP</li>
* <li>IDebugUIConstants.ID_RUN_LAUNCH_GROUP</li>
* <li>IDebugUIConstants.ID_PROFILE_LAUNCH_GROUP</li>
* </ul>
- * </p>
+ *
* @since 3.0
* @noimplement This interface is not intended to be implemented by clients.
* @noextend This interface is not intended to be extended by clients.
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ILaunchShortcut.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ILaunchShortcut.java
index b96dba546..c3adfdcf9 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ILaunchShortcut.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ILaunchShortcut.java
@@ -18,22 +18,21 @@ import org.eclipse.jface.viewers.ISelection;
import org.eclipse.ui.IEditorPart;
/**
- * A launch shortcut is capable of launching a selection
- * or active editor in the workbench. The delegate is responsible for
- * interpreting the selection or active editor (if it applies), and launching
- * an application. This may require creating a new launch configuration
- * with default values, or re-using an existing launch configuration.
+ * A launch shortcut is capable of launching a selection or active editor in the
+ * workbench. The delegate is responsible for interpreting the selection or
+ * active editor (if it applies), and launching an application. This may require
+ * creating a new launch configuration with default values, or re-using an
+ * existing launch configuration.
* <p>
- * A launch shortcut is defined as an extension
- * of type <code>org.eclipse.debug.ui.launchShortcuts</code>.
- * A shortcut specifies the perspectives in which is should be available
- * from the "Run/Debug" cascade menus.
+ * A launch shortcut is defined as an extension of type
+ * <code>org.eclipse.debug.ui.launchShortcuts</code>. A shortcut specifies the
+ * perspectives in which is should be available from the "Run/Debug" cascade
+ * menus.
* </p>
* <p>
- * A launch shortcut extension is defined in <code>plugin.xml</code>.
- * Following is an example definition of a launch shortcut extension.
+ * A launch shortcut extension is defined in <code>plugin.xml</code>. Following
+ * is an example definition of a launch shortcut extension.
* </p>
- * <br>
* <pre>
* &lt;extension point="org.eclipse.debug.ui.launchShortcuts"&gt;
* &lt;shortcut
@@ -78,50 +77,61 @@ import org.eclipse.ui.IEditorPart;
* &lt;/shortcut&gt;
* &lt;/extension&gt;
* </pre>
- * <br>
* <p>
* The attributes are specified as follows:
+ * </p>
* <ul>
- * <li><code>id</code> specifies a unique identifier for this launch shortcut.</li>
- * <li><code>modes</code> specifies a comma separated list of modes this shortcut
- * supports.</li>
- * <li><code>class</code> specifies a fully qualified name of a Java class
- * that implements <code>ILaunchShortcut</code>.</li>
+ * <li><code>id</code> specifies a unique identifier for this launch
+ * shortcut.</li>
+ * <li><code>modes</code> specifies a comma separated list of modes this
+ * shortcut supports.</li>
+ * <li><code>class</code> specifies a fully qualified name of a Java class that
+ * implements <code>ILaunchShortcut</code>.</li>
* <li><code>label</code> specifies a label used to render this shortcut.</li>
* <li><code>icon</code> specifies a plug-in relative path to an icon used to
- * render this shortcut.</li>
- * <li><code>category</code> specifies the launch configuration type category this shortcut is applicable for.
- * When unspecified, the category is <code>null</code> (default).</li>
- * <li><code>path</code> an optional menu path used to group launch shortcuts in menus.
- * Launch shortcuts are grouped alphabetically based on the <code>path</code> attribute,
- * and then sorted alphabetically within groups based on the <code>label</code> attribute.
- * When unspecified, a shortcut appears in the last group. This attribute was added in the 3.0.1 release.</li>
+ * render this shortcut.</li>
+ * <li><code>category</code> specifies the launch configuration type category
+ * this shortcut is applicable for. When unspecified, the category is
+ * <code>null</code> (default).</li>
+ * <li><code>path</code> an optional menu path used to group launch shortcuts in
+ * menus. Launch shortcuts are grouped alphabetically based on the
+ * <code>path</code> attribute, and then sorted alphabetically within groups
+ * based on the <code>label</code> attribute. When unspecified, a shortcut
+ * appears in the last group. This attribute was added in the 3.0.1
+ * release.</li>
* <li><code>helpContextId</code> optional attribute specifying the help context
* identifier to associate with the launch shortcut action in a menu.</li>
- * <li><code>description</code> Provides a human readable description of what the shortcut does (or will do)
- * if the user selects it. A Description provided in this field will apply as the default description for all
- * of the modes listed in the modes attribute.</li>
+ * <li><code>description</code> Provides a human readable description of what
+ * the shortcut does (or will do) if the user selects it. A Description provided
+ * in this field will apply as the default description for all of the modes
+ * listed in the modes attribute.</li>
* <li><code>perspective</code> has been <b>deprecated</b> in the 3.1 release.
- * The top level Run/Debug/Profile cascade menus now support contextual (selection sensitive)
- * launching, and clients should provide a <code>contextualLaunch</code> element instead.</li>
- * <li><code>contextualLaunch</code> holds all descriptions for adding shortcuts to the selection sensitive
- * Run/Debug/Profile cascade menus. Only objects that provide an <code>org.eclipse.debug.ui.actions.ILaunchable</code>
- * adapter are considered for the cascade menus. The <code>org.eclipse.debug.ui.actions.ILaunchable</code>
- * interface is simply used to tag objects that support contextual launching.</li>
- * <li><code>contextLabel</code> zero or more context menu labels. For
- * shortcuts that pass their filter tests, the specified label will appear
- * in the "Run ->" context menu and be bound to a launch action of the
- * specified mode (e.g. run,debug,profile).</li>
- * <li><code>configurationType</code> allows more that one associated launch configuration type to be
- * specified for this launch shortcut. That way consumers of launch shortcut information can know what kinds
- * of launch configurations your short is associated with/creates</li>
- * <li><code>description</code> allows a mode specific description(s) to be provided for this launch shortcut.</li>
+ * The top level Run/Debug/Profile cascade menus now support contextual
+ * (selection sensitive) launching, and clients should provide a
+ * <code>contextualLaunch</code> element instead.</li>
+ * <li><code>contextualLaunch</code> holds all descriptions for adding shortcuts
+ * to the selection sensitive Run/Debug/Profile cascade menus. Only objects that
+ * provide an <code>org.eclipse.debug.ui.actions.ILaunchable</code> adapter are
+ * considered for the cascade menus. The
+ * <code>org.eclipse.debug.ui.actions.ILaunchable</code> interface is simply
+ * used to tag objects that support contextual launching.</li>
+ * <li><code>contextLabel</code> zero or more context menu labels. For shortcuts
+ * that pass their filter tests, the specified label will appear in the "Run ->"
+ * context menu and be bound to a launch action of the specified mode (e.g.
+ * run,debug,profile).</li>
+ * <li><code>configurationType</code> allows more that one associated launch
+ * configuration type to be specified for this launch shortcut. That way
+ * consumers of launch shortcut information can know what kinds of launch
+ * configurations your short is associated with/creates</li>
+ * <li><code>description</code> allows a mode specific description(s) to be
+ * provided for this launch shortcut.</li>
* </ul>
- * </p>
* <p>
* <br>
- * Clients contributing a launch shortcut are intended to implement this interface.
+ * Clients contributing a launch shortcut are intended to implement this
+ * interface.
* </p>
+ *
* @since 2.0
*/
public interface ILaunchShortcut {
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ISourcePresentation.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ISourcePresentation.java
index 6823154e8..77659434a 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ISourcePresentation.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/ISourcePresentation.java
@@ -17,34 +17,33 @@ package org.eclipse.debug.ui;
import org.eclipse.ui.IEditorInput;
/**
- * A source presentation is used to resolve an editor in
- * which to display a debug model element, breakpoint, or
- * source element. By default, a debug model presentation
- * (which implements this interface) is used to resolve
- * editors when performing source lookup. However, a source
- * locator may override default editor resolution by implementing
- * this interface.
+ * A source presentation is used to resolve an editor in which to display a
+ * debug model element, breakpoint, or source element. By default, a debug model
+ * presentation (which implements this interface) is used to resolve editors
+ * when performing source lookup. However, a source locator may override default
+ * editor resolution by implementing this interface.
* <p>
- * Source lookup consists of the following steps:<ol>
- * <li>Locating a source element - the source locator associated
- * with a launch is queried for the source element associated
- * with a stack frame.</li>
- * <li>Resolving an editor in which to display a source element -
- * by default, the debug model presentation associated with the
- * debug model being debugged is queried for an editor input
- * and editor id in which to display a source element. However,
- * clients may override editor resolution by specifying a source
- * locator that is an instance of <code>ISourcePresentation</code>.
- * When a source presentation is specified as a source locator,
- * the source presentation is used to resolve an editor, rather
- * than the default debug model presentation.</li>
- * </ol>
+ * Source lookup consists of the following steps:
* </p>
+ * <ol>
+ * <li>Locating a source element - the source locator associated with a launch
+ * is queried for the source element associated with a stack frame.</li>
+ * <li>Resolving an editor in which to display a source element - by default,
+ * the debug model presentation associated with the debug model being debugged
+ * is queried for an editor input and editor id in which to display a source
+ * element. However, clients may override editor resolution by specifying a
+ * source locator that is an instance of <code>ISourcePresentation</code>. When
+ * a source presentation is specified as a source locator, the source
+ * presentation is used to resolve an editor, rather than the default debug
+ * model presentation.</li>
+ * </ol>
+ *
* <p>
* Clients may implement this interface as part of an
* {@link org.eclipse.debug.ui.IDebugModelPresentation} or as an optional
* extension to an {@link org.eclipse.debug.core.model.ISourceLocator}.
* </p>
+ *
* @since 2.0
*/
public interface ISourcePresentation {
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/BreakpointTypesContribution.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/BreakpointTypesContribution.java
index 3eed46a72..8c2340e5e 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/BreakpointTypesContribution.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/BreakpointTypesContribution.java
@@ -37,14 +37,17 @@ import org.eclipse.ui.menus.IWorkbenchContribution;
import org.eclipse.ui.services.IServiceLocator;
/**
- * Breakpoint ruler pop-up action that creates a sub-menu to select the currently
- * active breakpoint type. This menu contribution can be added to an editor
- * with the <code>org.eclipse.ui.menus</code> extension point. The breakpoint
- * types are calculated based on the toggle breakpoint target factories
- * contributed through the <code>toggleBreakpointsTargetFactories</code> extension point.
+ * Breakpoint ruler pop-up action that creates a sub-menu to select the
+ * currently active breakpoint type. This menu contribution can be added to an
+ * editor with the <code>org.eclipse.ui.menus</code> extension point. The
+ * breakpoint types are calculated based on the toggle breakpoint target
+ * factories contributed through the
+ * <code>toggleBreakpointsTargetFactories</code> extension point.
* <p>
- * Following is example plug-in XML used to contribute this action to an editor's
- * vertical ruler context menu.
+ * Following is example plug-in XML used to contribute this action to an
+ * editor's vertical ruler context menu.
+ * </p>
+ *
* <pre>
* &lt;extension point="org.eclipse.ui.menus"&gt;
* &lt;menuContribution
@@ -60,11 +63,12 @@ import org.eclipse.ui.services.IServiceLocator;
* &lt;/menu&gt;
* &lt;/menuContribution&gt;
* </pre>
- * </p>
+ *
* <p>
- * Clients may refer to this class in plug-in XML. This class
- * is not intended to be sub-classed.
+ * Clients may refer to this class in plug-in XML. This class is not intended to
+ * be sub-classed.
* </p>
+ *
* @since 3.8
* @noextend This class is not intended to be sub-classed by clients.
*/
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/IAddMemoryRenderingsTarget.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/IAddMemoryRenderingsTarget.java
index 418b9ec5b..e33c28e1c 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/IAddMemoryRenderingsTarget.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/IAddMemoryRenderingsTarget.java
@@ -21,24 +21,29 @@ import org.eclipse.ui.IWorkbenchPart;
/**
* Adapter for the platform's retargettable "add memory rendering" action.
- * Clients implementing this adapter are expected to add the necessary memory blocks
- * and renderings when the adapter is invoked.
+ * Clients implementing this adapter are expected to add the necessary memory
+ * blocks and renderings when the adapter is invoked.
* <p>
* Typically, to add a memory rendering, client needs to do the following:
+ * </p>
* <ol>
* <li>Create a new memory block</li>
- * <li>Add the new memory block to the Memory Block Manager. (<code>IMemoryBlockManager</code>)</li>
- * <li>Create the new rendering from <code>IMemoryRenderingTypeDelegate</code></li>
- * <li>Bring the required memory view to the top. (<code>IMemoryRenderingSite</code>)</li>
+ * <li>Add the new memory block to the Memory Block Manager.
+ * (<code>IMemoryBlockManager</code>)</li>
+ * <li>Create the new rendering from
+ * <code>IMemoryRenderingTypeDelegate</code></li>
+ * <li>Bring the required memory view to the top.
+ * (<code>IMemoryRenderingSite</code>)</li>
* <li>Find the container from the memory view to host the new memory rendering.
- * (<code>IMemoryRenderingContainer</code>)</li>
- * <li>Initialize the new rendering with the appropriate memory block and container.</li>
+ * (<code>IMemoryRenderingContainer</code>)</li>
+ * <li>Initialize the new rendering with the appropriate memory block and
+ * container.</li>
* <li>Add the new rendering to the container.</li>
* </ol>
- * </p>
* <p>
* Clients may implement this interface.
* </p>
+ *
* @since 3.2
* @see AddMemoryRenderingActionDelegate
*/
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/ILaunchable.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/ILaunchable.java
index fd68c9e07..a24060803 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/ILaunchable.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/ILaunchable.java
@@ -14,56 +14,60 @@
package org.eclipse.debug.ui.actions;
/**
- * Interface used to tag objects as launchable. Objects that provide
- * an adapter of this type will be considered by the contextual
- * launch support.
+ * Interface used to tag objects as launchable. Objects that provide an adapter
+ * of this type will be considered by the contextual launch support.
* <p>
* The debug platform uses the {@link ILaunchable} interface as a tag for
* objects that can be launched via the context menu 'Run As / Debug As' actions
* and run/debug tool bar buttons. The platform checks if an {@link ILaunchable}
* adapter is available from the selection/active editor to determine if it
* should be considered for launching. However, the platform never actually
- * retrieves the adapter or calls any methods on it (the interface is, in fact, empty).
+ * retrieves the adapter or calls any methods on it (the interface is, in fact,
+ * empty).
+ * </p>
+ * <p>
+ * The debug platform performs the following test:
* </p>
- * <p>The debug platform performs the following test:</p>
* <ul>
* <li>
* <code>Platform.getAdapterManager().hasAdapter(X, ILaunchable.class.getName());</code>
* </li>
* </ul>
* <p>
- * Thus objects that can be launched need to register {@link ILaunchable} adapters, but
- * don't have to provide implementations. There is also no harm in implementing the interface
- * or providing the adapter. For example, JDT contributes an adapter as follows. Although
- * no adapter is actually provided the platform will answer <code>true</code> to
- * <code>hasAdapter(...)</code>.
+ * Thus objects that can be launched need to register {@link ILaunchable}
+ * adapters, but don't have to provide implementations. There is also no harm in
+ * implementing the interface or providing the adapter. For example, JDT
+ * contributes an adapter as follows. Although no adapter is actually provided
+ * the platform will answer <code>true</code> to <code>hasAdapter(...)</code>.
* </p>
+ *
* <pre>
- * <extension point="org.eclipse.core.runtime.adapters">
- * <factory
+ * &lt;extension point="org.eclipse.core.runtime.adapters"&gt;
+ * &lt;factory
* class=""
- * adaptableType="org.eclipse.jdt.core.IJavaElement">
- * <adapter type="org.eclipse.debug.ui.actions.ILaunchable"/>
- * </factory>
+ * adaptableType="org.eclipse.jdt.core.IJavaElement"&gt;
+ * &lt;adapter type="org.eclipse.debug.ui.actions.ILaunchable"/&gt;
+ * &lt;/factory&gt;
+ * &lt;/extension&gt;
* </pre>
* <p>
- * Clients may contribute an adapter of this type for launchable objects
- * via the <code>org.eclipse.core.runtime.adapters</code> extension
- * point. A factory and implementation of this interface are not actually
- * required.
+ * Clients may contribute an adapter of this type for launchable objects via the
+ * <code>org.eclipse.core.runtime.adapters</code> extension point. A factory and
+ * implementation of this interface are not actually required.
* </p>
* <p>
- * Clients that need to check for presence of launchable adapter using
- * standard expression mechanism, should use a property tester as follows:
+ * Clients that need to check for presence of launchable adapter using standard
+ * expression mechanism, should use a property tester as follows:
+ * </p>
+ *
* <pre>
- * <with variable="selection">
- * <iterator operator="and" ifEmpty="false">
- * <test property="org.eclipse.debug.core.launchable" value="debug"/>
- * </iterator>
- * </with>
+ * &lt;with variable="selection"&gt;
+ * &lt;iterator operator="and" ifEmpty="false"&gt;
+ * &lt;test property="org.eclipse.debug.core.launchable" value="debug"/&gt;
+ * &lt;/iterator&gt;
+ * &lt;/with&gt;
* </pre>
*
- * </p>
* @see org.eclipse.debug.ui.actions.ContextualLaunchAction
* @since 3.0
*/
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/IToggleBreakpointsTargetFactory.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/IToggleBreakpointsTargetFactory.java
index a69f37a40..6b7a25b79 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/IToggleBreakpointsTargetFactory.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/IToggleBreakpointsTargetFactory.java
@@ -21,14 +21,16 @@ import org.eclipse.ui.IWorkbenchPart;
/**
* A toggle breakpoints target factory creates one or more toggle breakpoint
- * targets. The toggle breakpoints targets are used by toggle breakpoint actions
- * to create breakpoints appropriate for the active editor, debug session, project,
- * or selection.
+ * targets. The toggle breakpoints targets are used by toggle breakpoint actions
+ * to create breakpoints appropriate for the active editor, debug session,
+ * project, or selection.
*
* <p>
* Toggle breakpoints target factories are contributed via the
- * <code>org.eclipse.debug.ui.toggleBreakpointsTargetFactories</code>
- * extension point. Following is an example of a detail pane factory extension:
+ * <code>org.eclipse.debug.ui.toggleBreakpointsTargetFactories</code> extension
+ * point. Following is an example of a detail pane factory extension:
+ * </p>
+ *
* <pre>
* &lt;extension point="org.eclipse.debug.ui.toggleBreakpointsTargetFactories"&gt;
* &lt;toggleTargetFactory
@@ -54,12 +56,11 @@ import org.eclipse.ui.IWorkbenchPart;
* &lt;/toggleTargetFactory&gt;
* &lt;/extension&gt;
* </pre>
- * </p>
- * <p>
- * <p>
+ *
* Clients contributing a toggle breakpoints target factory are intended to
* implement this interface.
*
+ *
* @see IToggleBreakpointsTarget
* @see IToggleBreakpointsTargetExtension
* @see org.eclipse.debug.ui.actions.IToggleBreakpointsTargetManager
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/IVariableValueEditor.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/IVariableValueEditor.java
index 2e234c9d3..b6f7c962e 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/IVariableValueEditor.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/IVariableValueEditor.java
@@ -17,11 +17,13 @@ import org.eclipse.debug.core.model.IVariable;
import org.eclipse.swt.widgets.Shell;
/**
- * A variable value editor allows the user to edit a variable's value.
- * Variable value editors are contributed for a debug model via the
+ * A variable value editor allows the user to edit a variable's value. Variable
+ * value editors are contributed for a debug model via the
* <code>org.eclipse.debug.ui.variableValueEditors</code> extension point.
* <p>
* Following is example plug-in XML for contributing a variable value editor.
+ * </p>
+ *
* <pre>
* &lt;extension point="org.eclipse.debug.ui.variableValueEditors"&gt;
* &lt;variableEditor
@@ -29,6 +31,7 @@ import org.eclipse.swt.widgets.Shell;
* class="com.examples.variables.MyVariableValueEditor"/&gt;
* &lt;/extension&gt;
* </pre>
+ *
* The attributes are specified as follows:
* <ul>
* <li><code>modelId</code> the debug model identifier for which the given
@@ -36,10 +39,10 @@ import org.eclipse.swt.widgets.Shell;
* <li><code>class</code> fully qualified name of a class that implements
* {@link IVariableValueEditor}</li>
* </ul>
- * </p>
* <p>
* Clients may implement this interface.
* </p>
+ *
* @since 3.1
*/
public interface IVariableValueEditor {
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerBreakpointTypesActionDelegate.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerBreakpointTypesActionDelegate.java
index 744acc057..eb72e8932 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerBreakpointTypesActionDelegate.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerBreakpointTypesActionDelegate.java
@@ -42,16 +42,19 @@ import org.eclipse.ui.texteditor.ITextEditor;
import org.eclipse.ui.texteditor.ITextEditorExtension;
/**
- * Breakpoint ruler pop-up action that creates a sub-menu to select the currently
- * active breakpoint type. This action delegate can be contributed to an editor
- * with the <code>editorActions</code> extension point. The breakpoint types are
- * calculated based on the toggle breakpoint target factories contributed through
- * the <code>toggleBreakpointsTargetFactories</code> extension point.
+ * Breakpoint ruler pop-up action that creates a sub-menu to select the
+ * currently active breakpoint type. This action delegate can be contributed to
+ * an editor with the <code>editorActions</code> extension point. The breakpoint
+ * types are calculated based on the toggle breakpoint target factories
+ * contributed through the <code>toggleBreakpointsTargetFactories</code>
+ * extension point.
* <p>
- * Following is example plug-in XML used to contribute this action to an editor's
- * vertical ruler context menu. It uses the <code>popupMenus</code> extension
- * point, by referencing the ruler's context menu identifier in the
+ * Following is example plug-in XML used to contribute this action to an
+ * editor's vertical ruler context menu. It uses the <code>popupMenus</code>
+ * extension point, by referencing the ruler's context menu identifier in the
* <code>targetID</code> attribute.
+ * </p>
+ *
* <pre>
* &lt;extension point="org.eclipse.ui.popupMenus"&gt;
* &lt;viewerContribution
@@ -65,11 +68,11 @@ import org.eclipse.ui.texteditor.ITextEditorExtension;
* &lt;/action&gt;
* &lt;/viewerContribution&gt;
* </pre>
- * </p>
* <p>
- * Clients may refer to this class as an action delegate in plug-in XML. This class
- * is not intended to be subclassed.
+ * Clients may refer to this class as an action delegate in plug-in XML. This
+ * class is not intended to be subclassed.
* </p>
+ *
* @see IToggleBreakpointsTargetManager
* @see IToggleBreakpointsTargetFactory
* @noextend This class is not intended to be subclassed by clients.
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerEnableDisableBreakpointActionDelegate.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerEnableDisableBreakpointActionDelegate.java
index e11712b41..e27e253ab 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerEnableDisableBreakpointActionDelegate.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerEnableDisableBreakpointActionDelegate.java
@@ -37,7 +37,6 @@ import org.eclipse.ui.texteditor.ITextEditor;
* &lt;/action&gt;
* &lt;/viewerContribution&gt;
* </pre>
- * </p>
* <p>
* Clients may refer to this class as an action delegate in plug-in XML.
* </p>
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerRunToLineActionDelegate.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerRunToLineActionDelegate.java
index dee514460..f3abc61fe 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerRunToLineActionDelegate.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerRunToLineActionDelegate.java
@@ -29,6 +29,7 @@ import org.eclipse.ui.texteditor.ITextEditor;
* Following is example plug-in XML used to contribute this action to an editor.
* Note that the label attribute of this action is not displayed in the editor.
* Instead, the label of the created action is displayed.
+ * </p>
*
* <pre>
* &lt;extension point="org.eclipse.ui.editorActions"&gt;
@@ -44,11 +45,11 @@ import org.eclipse.ui.texteditor.ITextEditor;
* &lt;/editorContribution&gt;
* &lt;/extension&gt;
* </pre>
- * </p>
* <p>
* This action can also be contributed to a vertical ruler context menu via the
* <code>popupMenus</code> extension point, by referencing the ruler's context
* menu identifier in the <code>targetID</code> attribute.
+ * </p>
*
* <pre>
* &lt;extension point="org.eclipse.ui.popupMenus"&gt;
@@ -63,7 +64,6 @@ import org.eclipse.ui.texteditor.ITextEditor;
* &lt;/action&gt;
* &lt;/viewerContribution&gt;
* </pre>
- * </p>
* <p>
* Clients may refer to this class as an action delegate in plug-in XML.
* </p>
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerToggleBreakpointActionDelegate.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerToggleBreakpointActionDelegate.java
index 5734d194e..5469fa3cb 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerToggleBreakpointActionDelegate.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RulerToggleBreakpointActionDelegate.java
@@ -13,27 +13,26 @@
*******************************************************************************/
package org.eclipse.debug.ui.actions;
-import org.eclipse.swt.widgets.Event;
-
import org.eclipse.jface.action.IAction;
-
import org.eclipse.jface.text.source.IVerticalRulerInfo;
-
+import org.eclipse.swt.widgets.Event;
import org.eclipse.ui.IActionDelegate2;
import org.eclipse.ui.IEditorPart;
import org.eclipse.ui.texteditor.AbstractRulerActionDelegate;
import org.eclipse.ui.texteditor.ITextEditor;
/**
- * Toggles a breakpoint when ruler is double-clicked. This action delegate can be
- * contributed to an editor with the <code>editorActions</code> extension point.
- * This action is as a factory that creates another action that performs the
- * actual breakpoint toggling. The created action acts on the editor's
+ * Toggles a breakpoint when ruler is double-clicked. This action delegate can
+ * be contributed to an editor with the <code>editorActions</code> extension
+ * point. This action is as a factory that creates another action that performs
+ * the actual breakpoint toggling. The created action acts on the editor's
* <code>IToggleBreakpointsTagret</code> to toggle breakpoints.
* <p>
* Following is example plug-in XML used to contribute this action to an editor.
* Note that the label attribute of this action is not displayed in the editor.
* Instead, the label of the created action is displayed.
+ * </p>
+ *
* <pre>
* &lt;extension point="org.eclipse.ui.editorActions"&gt;
* &lt;editorContribution
@@ -48,11 +47,12 @@ import org.eclipse.ui.texteditor.ITextEditor;
* &lt;/editorContribution&gt;
* &lt;/extension&gt;
* </pre>
- * </p>
* <p>
* This action can also be contributed to a vertical ruler context menu via the
* <code>popupMenus</code> extension point, by referencing the ruler's context
* menu identifier in the <code>targetID</code> attribute.
+ * </p>
+ *
* <pre>
* &lt;extension point="org.eclipse.ui.popupMenus"&gt;
* &lt;viewerContribution
@@ -66,10 +66,10 @@ import org.eclipse.ui.texteditor.ITextEditor;
* &lt;/action&gt;
* &lt;/viewerContribution&gt;
* </pre>
- * </p>
* <p>
* Clients may refer to this class as an action delegate in plug-in XML.
* </p>
+ *
* @since 3.1
* @noextend This class is not intended to be subclassed by clients.
* @noinstantiate This class is not intended to be instantiated by clients.
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RunAction.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RunAction.java
index 775d8a990..06753e5e2 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RunAction.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/actions/RunAction.java
@@ -22,7 +22,6 @@ import org.eclipse.debug.ui.IDebugUIConstants;
* Action to launch the last launch configuration that was successfully
* launched, in run mode. If no configurations have been launched, the launch
* configuration dialog is opened.
- * </p>
* <p>
* This class may be instantiated.
* </p>
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/console/IConsoleColorProvider.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/console/IConsoleColorProvider.java
index 724e9cd70..c0531a590 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/console/IConsoleColorProvider.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/console/IConsoleColorProvider.java
@@ -27,8 +27,9 @@ import org.eclipse.swt.graphics.Color;
* <code>IProcess. ATTR_PROCESS_TYPE</code>.
* <p>
* A console color provider extension is defined in <code>plugin.xml</code>.
- * Following is an example definition of a console color
- * provider extension.
+ * Following is an example definition of a console color provider extension.
+ * </p>
+ *
* <pre>
* &lt;extension point="org.eclipse.debug.ui.consoleColorProviders"&gt;
* &lt;consoleColorProvider
@@ -38,19 +39,21 @@ import org.eclipse.swt.graphics.Color;
* &lt;/consoleColorProvider&gt;
* &lt;/extension&gt;
* </pre>
+ *
* The attributes are specified as follows:
* <ul>
- * <li><code>id</code> specifies a unique identifier for this color provider.</li>
- * <li><code>class</code> specifies a fully qualified name of a Java class
- * that implements <code>IConsoleColorProvider</code>.</li>
+ * <li><code>id</code> specifies a unique identifier for this color
+ * provider.</li>
+ * <li><code>class</code> specifies a fully qualified name of a Java class that
+ * implements <code>IConsoleColorProvider</code>.</li>
* <li><code>processType</code> specifies the identifier of the process type
* this content provider is associated with (which corresponds to the
* <code>ATTR_PROCESS_TYPE</code> attribute on a process).</li>
* </ul>
- * </p>
* <p>
* Clients may implement this interface.
* </p>
+ *
* @since 2.1
*/
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/memory/IMemoryRendering.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/memory/IMemoryRendering.java
index 13d632c42..67785cc9f 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/memory/IMemoryRendering.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/memory/IMemoryRendering.java
@@ -25,6 +25,8 @@ import org.eclipse.swt.widgets.Control;
* via the <code>memoryRenderings</code> extension point.
* <p>
* Following is an example definition of a memory renderings extension.
+ * </p>
+ *
* <pre>
* &lt;extension point="org.eclipse.debug.ui.memoryRenderings"&gt;
* &lt;memoryRenderingType
@@ -34,38 +36,41 @@ import org.eclipse.swt.widgets.Control;
* &lt;/memoryRenderingType&gt;
* &lt;/extension&gt;
* </pre>
+ *
* The attributes are specified as follows:
* <ul>
- * <li><code>id</code> specifies a unique identifier for a type of memory rendering</li>
- * <li><code>name</code> specifies a human readable label for a rendering type</li>
+ * <li><code>id</code> specifies a unique identifier for a type of memory
+ * rendering</li>
+ * <li><code>name</code> specifies a human readable label for a rendering
+ * type</li>
* <li><code>class</code> specifies the fully qualified name of the Java class
- * that implements <code>IMemoryRenderingTypeDelegate</code>. Renderings are created
- * via this factory.</li>
+ * that implements <code>IMemoryRenderingTypeDelegate</code>. Renderings are
+ * created via this factory.</li>
* </ul>
- * </p>
* <p>
- * A rendering provides an image and label. To support dynamic labels and images, property
- * change notification is used with the following property constants defined in
- * <code>IBasicPropertyConstants</code>:
+ * A rendering provides an image and label. To support dynamic labels and
+ * images, property change notification is used with the following property
+ * constants defined in <code>IBasicPropertyConstants</code>:
+ * </p>
* <ul>
* <li><code>P_TEXT</code> - indicates a label change</li>
* <li><code>P_IMAGE</code> - indicates a image change</li>
* </ul>
- * </p>
* <p>
* Renderings needing to synchronize with other renderings are intended to use
- * property change notifications via its synchronization service. For example, when a
- * rendering becomes visible, it can register for property change events with its rendering
- * site's synchronization service, and when it becomes hidden it can unregister. When a
- * rendering is activated, it should set itself as the synchrnoization provider in its
- * rendering site and fire property change events to communicate information to
- * interested listeners.
+ * property change notifications via its synchronization service. For example,
+ * when a rendering becomes visible, it can register for property change events
+ * with its rendering site's synchronization service, and when it becomes hidden
+ * it can unregister. When a rendering is activated, it should set itself as the
+ * synchrnoization provider in its rendering site and fire property change
+ * events to communicate information to interested listeners.
* </p>
* <p>
- * Clients contributing a memory rendering type are intended to implement this interface
- * and <code>IMemoryRenderingTypeDelegate</code>. The factory will be used to create instances
- * of <code>IMemoryRendering</code>.
+ * Clients contributing a memory rendering type are intended to implement this
+ * interface and <code>IMemoryRenderingTypeDelegate</code>. The factory will be
+ * used to create instances of <code>IMemoryRendering</code>.
* </p>
+ *
* @since 3.1
*/
public interface IMemoryRendering extends IAdaptable{
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/memory/IMemoryRenderingSynchronizationService.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/memory/IMemoryRenderingSynchronizationService.java
index 351b0dfc1..dbcd2e94b 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/memory/IMemoryRenderingSynchronizationService.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/memory/IMemoryRenderingSynchronizationService.java
@@ -66,10 +66,10 @@ public interface IMemoryRenderingSynchronizationService {
void setSynchronizationProvider(IMemoryRendering rendering);
/**
- * Returns the rendering currently providing synchronization information for
- * this synchronization service, or <code>null</code if none.
- *
- * @return rendering providing synchronization information or <code>null</code>
- */
+ * Returns the rendering currently providing synchronization information for
+ * this synchronization service, or <code>null</code> if none.
+ *
+ * @return rendering providing synchronization information or <code>null</code>
+ */
IMemoryRendering getSynchronizationProvider();
}
diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/sourcelookup/ISourceContainerBrowser.java b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/sourcelookup/ISourceContainerBrowser.java
index 86c154a3b..e6d7be9cb 100644
--- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/sourcelookup/ISourceContainerBrowser.java
+++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/sourcelookup/ISourceContainerBrowser.java
@@ -19,13 +19,15 @@ import org.eclipse.swt.widgets.Shell;
/**
- * Creates and edits source containers for a source lookup director.
- * Contributed via a source container presentation extension for
- * a specific type of source container.
+ * Creates and edits source containers for a source lookup director. Contributed
+ * via a source container presentation extension for a specific type of source
+ * container.
* <p>
- * Following is an example source container presentation definition
- * that contributes a source container browser via the
- * <code>browserClass</code> attribute.
+ * Following is an example source container presentation definition that
+ * contributes a source container browser via the <code>browserClass</code>
+ * attribute.
+ * </p>
+ *
* <pre>
* &lt;extension point=&quot;org.eclipse.debug.ui.sourceContainerPresentations&quot;&gt;
* &lt;sourceContainerPresentation
@@ -36,7 +38,7 @@ import org.eclipse.swt.widgets.Shell;
* &lt;/sourceContainerPresentation&gt;
* &lt;/extension&gt;
* </pre>
- * </p>
+ *
* @since 3.0
*/
public interface ISourceContainerBrowser {

Back to the top