Bug 543933 - Build javadocs with Java 11
Fix javadoc warnings catched by Java 11 tool with XDoclint:html.
Change-Id: Iefef0a39757f5b420d57e6a70c422b6a630f0e42
Signed-off-by: Alexander Kurtakov <akurtako@redhat.com>
diff --git a/bundles/org.eclipse.jface/src/org/eclipse/jface/action/package.html b/bundles/org.eclipse.jface/src/org/eclipse/jface/action/package.html
index b9f7ac7..53bde93 100644
--- a/bundles/org.eclipse.jface/src/org/eclipse/jface/action/package.html
+++ b/bundles/org.eclipse.jface/src/org/eclipse/jface/action/package.html
@@ -12,19 +12,19 @@
<h2>
Package Specification</h2>
Contribution managers coordinate contributions to shared UI resources such
-as menus, menu bars, tool bars, and status lines. <tt>ContributionManager</tt>
-maintains the contributions as a dynamic list of contribution items (<tt>IContributionItems</tt>).
-Separators (<tt>Separator</tt>) can be included in contribution lists to
+as menus, menu bars, tool bars, and status lines. <code>ContributionManager</code>
+maintains the contributions as a dynamic list of contribution items (<code>IContributionItems</code>).
+Separators (<code>Separator</code>) can be included in contribution lists to
break up the list's visual representation. Internally, contribution lists
-can be organized into named groups via special group markers (<tt>GroupMarker</tt>)
+can be organized into named groups via special group markers (<code>GroupMarker</code>)
to facilitate programatic insertion at specific positions within the list.
<p>Three specific contribution managers are provided: a status line manager
-(<tt>StatusLineManager</tt>), a tool bar manager (<tt>ToolBarManager</tt>),
-and a hierarchical menu manager (<tt>MenuManager</tt>).
-<p>Actions (<tt>IAction</tt>) are commands which can be triggered from
+(<code>StatusLineManager</code>), a tool bar manager (<code>ToolBarManager</code>),
+and a hierarchical menu manager (<code>MenuManager</code>).
+<p>Actions (<code>IAction</code>) are commands which can be triggered from
the UI, like the ones found in menus, toolbars, and buttons. Menus and
tools bars are typically populated with contribution items that delegate
-to actions (<tt>ActionContributionItem</tt>).
+to actions (<code>ActionContributionItem</code>).
<p>Note: None of the classes in this package maintain global state.
<br>
</body>
diff --git a/bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/package.html b/bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/package.html
index 7e6c849..458335c 100644
--- a/bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/package.html
+++ b/bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/package.html
@@ -14,20 +14,20 @@
This package provides classes that can be used to guide a dialog user through choosing
appropriate content for fields in a dialog or wizard.
<p>
-A <tt>ContentProposalAdapter</tt> can be attached to an arbitrary control to provide
+A <code>ContentProposalAdapter</code> can be attached to an arbitrary control to provide
a popup showing content proposals. These proposals appear when the defined
-assist keystroke is invoked. The <tt>ContentProposalAdapter</tt> manages the creation,
+assist keystroke is invoked. The <code>ContentProposalAdapter</code> manages the creation,
hiding, and showing of the proposal popup, as well as the proper handling of key events
-between the adapted control and its popup. Implementors of <tt>IControlContentAdapter</tt>
+between the adapted control and its popup. Implementors of <code>IControlContentAdapter</code>
allow the adapter to set and retrieve the contents of the supplied control.
</p>
<p>
-An <tt>AutoCompleteField</tt> configures a <tt>ContentProposalAdapter</tt> in a manner
+An <code>AutoCompleteField</code> configures a <code>ContentProposalAdapter</code> in a manner
that supports automatic field completion popups that filter based on the control's
contents.
</p>
<p>
-<tt>ControlDecoration</tt> can be used to decorate an arbitrary control with
+<code>ControlDecoration</code> can be used to decorate an arbitrary control with
an image that communicates information about the control's content. Decorations can be
used to show additional information about a field, such as its status, or a cue
that shows availability of content proposals. Decorations are defined in pre-defined
@@ -37,7 +37,7 @@
descriptive text when the user hovers over them.
</p>
<p>
-<tt>DecoratedField</tt> can also be used to decorate a control. The main difference
+<code>DecoratedField</code> can also be used to decorate a control. The main difference
is that decorated fields reserve space for multiple decorations in particular
locations around the control. To do this, the field manages the creation of the
field's control, using a specialized layout to ensure there is adequate space
diff --git a/bundles/org.eclipse.jface/src/org/eclipse/jface/operation/package.html b/bundles/org.eclipse.jface/src/org/eclipse/jface/operation/package.html
index 1680896..c4dd2ec 100644
--- a/bundles/org.eclipse.jface/src/org/eclipse/jface/operation/package.html
+++ b/bundles/org.eclipse.jface/src/org/eclipse/jface/operation/package.html
@@ -15,12 +15,12 @@
most controls and displaying a busy cursor and progress indicator; while
the operation is in progress, the only requests that will be accepted will
be ones to cancel the operation.
-<p>The <tt>IRunnableWithProgress</tt> interface should be implemented by
+<p>The <code>IRunnableWithProgress</code> interface should be implemented by
any class whose instances are intended to be executed as long-running operations.
-These objects can then be run in any runnable context (<tt>IRunnableContext</tt>),
-including such standard JFace UI components as application windows (<tt>ApplicationWindow</tt>),
-wizard dialogs (<tt>WizardDialog</tt>), and progress monitor dialogs (<tt>ProgressMonitorDialog</tt>).
-The utility class <tt>ModalContext</tt> defines the basic mechanism and
+These objects can then be run in any runnable context (<code>IRunnableContext</code>),
+including such standard JFace UI components as application windows (<code>ApplicationWindow</code>),
+wizard dialogs (<code>WizardDialog</code>), and progress monitor dialogs (<code>ProgressMonitorDialog</code>).
+The utility class <code>ModalContext</code> defines the basic mechanism and
UI event loop for modal operations.
</body>
</html>
diff --git a/bundles/org.eclipse.jface/src/org/eclipse/jface/preference/package.html b/bundles/org.eclipse.jface/src/org/eclipse/jface/preference/package.html
index 0ddc967..8172c61 100644
--- a/bundles/org.eclipse.jface/src/org/eclipse/jface/preference/package.html
+++ b/bundles/org.eclipse.jface/src/org/eclipse/jface/preference/package.html
@@ -10,19 +10,19 @@
Provides a framework for preferences.
<h2>
Package Specification</h2>
-A <b>preference manager</b> (class <tt>PreferenceManager</tt>) maintains
+A <b>preference manager</b> (class <code>PreferenceManager</code>) maintains
a tree of <b>preference nodes</b>. Preferences are presented to the end
user in a <b>preference dialog</b> consisting of <b>preference pages</b>.
A preference page consists of multiple preference fields, which can be
displayed and modified though <b>field editors</b>. The framework contains
-an abstract base class for preference dialogs (<tt>PreferenceDialog</tt>),
-and an abstract preference page class (<tt>FieldEditorPreferencePage</tt>)
+an abstract base class for preference dialogs (<code>PreferenceDialog</code>),
+and an abstract preference page class (<code>FieldEditorPreferencePage</code>)
for hosting these field editors.
<p>The individual preference values are maintained in a <b>preference store</b>
-(<tt>IPreferenceStore</tt>). Each preference has a current value and a
+(<code>IPreferenceStore</code>). Each preference has a current value and a
default value use to (re-)initialize it. The framework provides a concrete
-preference store implementation (<tt>PreferenceStore</tt>) based on an
-internal <tt>java.util.Properties</tt> object, with support for persisting
+preference store implementation (<code>PreferenceStore</code>) based on an
+internal <code>java.util.Properties</code> object, with support for persisting
the non-default preference values to files or streams.
<p>A field editor presents the value of a single preference to the end
user. The value is loaded from the preference store; if modified by the
@@ -32,36 +32,35 @@
preferences:
<ul>
<li>
-<tt>BooleanFieldEditor</tt> - booleans</li>
+<code>BooleanFieldEditor</code> - booleans</li>
<li>
-<tt>IntegerFieldEditor</tt> - integers</li>
+<code>IntegerFieldEditor</code> - integers</li>
<li>
-<tt>StringFieldEditor</tt> - text strings</li>
+<code>StringFieldEditor</code> - text strings</li>
<li>
-<tt>RadioGroupFieldEditor</tt> - enumerations</li>
+<code>RadioGroupFieldEditor</code> - enumerations</li>
<li>
-<tt>ColorFieldEditor</tt> - RGB colors</li>
+<code>ColorFieldEditor</code> - RGB colors</li>
<li>
-<tt>FontFieldEditor</tt> - fonts</li>
+<code>FontFieldEditor</code> - fonts</li>
<li>
-<tt>DirectoryFieldEditor</tt> - directories</li>
+<code>DirectoryFieldEditor</code> - directories</li>
<li>
-<tt>FileFieldEditor</tt> - files</li>
+<code>FileFieldEditor</code> - files</li>
<li>
-<tt>PathEditor</tt> - paths</li>
+<code>PathEditor</code> - paths</li>
</ul>
-All field editors are subclasses of the abstract base class <tt>FieldEditor</tt>;
+All field editors are subclasses of the abstract base class <code>FieldEditor</code>;
the framework allows new kinds of field editors to be defined by subclassing
this class or one of its subclasses.
<p>Note: None of the classes in this package maintain global state.
-<br>
</body>
</html>
