highlighting in inspection descriptions

2026-09-27 10:03:11 +07:00 · 2011-02-10 15:47:42 +01:00
parent 5a57334d4f
commit f917e004c1
8 changed files with 8 additions and 8 deletions
@@ -1,6 +1,6 @@
 <html>
 <body>
-This inspection reports any calls to Integer.getInteger() or Boolean.getBoolean().
+This inspection reports any calls to <b>Integer.getInteger()</b> or <b>Boolean.getBoolean()</b>.
 These methods fetch integer and boolean values from the
 system properties for a given key. Due to their underexpressive names and confusing
 location of functionality, it's easy for novice programmers to attempt to use these
@@ -1,6 +1,6 @@
 <html>
 <body>
-This inspection reports calls to java.lang.Thread.sleep() that occur inside loops. Such calls
+This inspection reports calls to <b>java.lang.Thread.sleep()</b> that occur inside loops. Such calls
 are indicative of "busy-waiting". Busy-waiting is often inefficient, and may result in unexpected deadlocks
 as busy-waiting threads do not release locked resources.
 <p>
@@ -7,7 +7,7 @@ to wrap the initial exception, so that valuable context information
 such as stack frames and line numbers are not lost.
 <p>
 Use the checkbox below to indicate if the inspection should ignore exceptions which
-receive the result of a method call on the original exception, such as 'getMessage()',
+receive the result of a method call on the original exception, such as <b>getMessage()</b>,
 as an argument.
 <p>
 <small>Powered by InspectionGadgets</small>
@@ -5,7 +5,7 @@ with too many return points may be confusing, and hard to refactor.
 <p>
 Use the field provided below to specify the maximum acceptable number of return points a method might have.
 Use the check boxes below to specify if guard clause and/or return points inside 
-equals() methods should be ignored.
+<b>equals()</b> methods should be ignored.
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,7 +2,7 @@
 <body>
 This inspection reports any calls of overridable methods of the current class during object construction.
 An object is constructed inside a constructor, an instance initializer or
-inside a clone(), readObject() or readObjectNoData() method.
+inside a <b>clone()</b>, <b>readObject()</b> or <b>readObjectNoData()</b> method.
 Methods are overridable if they are not declared <b>final</b>,
 <b>static</b> or <b>private</b>.
 Such calls may result in subtle bugs, as the object is not guaranteed to be initialized
@@ -2,7 +2,7 @@
 <body>
 This inspection reports any calls of overridden methods of the current class during object construction.
 An object is constructed inside a constructor, an instance initializer or
-inside a clone(), readObject() or readObjectNoData() method.
+inside a <b>clone()</b>, <b>readObject()</b> or <b>readObjectNoData()</b> method.
 Such calls may result in subtle bugs, as the object is not guaranteed to be initialized
 before the method call occurs.
 <p>
@@ -1,6 +1,6 @@
 <html>
 <body>
-This inspection reports any calls to String.format() where only a format string is
+This inspection reports any calls to <b>String.format()</b> where only a format string is
 provided, but no arguments. Such a call is unnecessary and can be replaced with just
 the string.
 <p>
@@ -2,7 +2,7 @@
 <body>
 This inspection reports static method calls where the call is qualified
 by a subclass of the declaring class, rather than the declaring class itself
-(e.g. MyThreadSubclass.sleep()). Java allows such qualification, but such calls
+(e.g. <b>MyThreadSubclass.sleep()</b>). Java allows such qualification, but such calls
 may be confusing, and may indicate a subtle confusion of inheritance and overriding.
 <p>
 <small>Powered by InspectionGadgets</small>