[Fb-contrib-commit] SF.net SVN: fb-contrib:[1444] trunk/fb-contrib/etc/messages.xml

[<dbr...@us...>]

Revision: 1444
          http://fb-contrib.svn.sourceforge.net/fb-contrib/?rev=1444&view=rev
Author:   dbrosius
Date:     2010-01-05 08:35:57 +0000 (Tue, 05 Jan 2010)

Log Message:
-----------
update from Chris Peterson to fix the {2}'s showing up in the gui description panels

Modified Paths:
--------------
    trunk/fb-contrib/etc/messages.xml

Modified: trunk/fb-contrib/etc/messages.xml
===================================================================
--- trunk/fb-contrib/etc/messages.xml	2010-01-05 07:11:47 UTC (rev 1443)
+++ trunk/fb-contrib/etc/messages.xml	2010-01-05 08:35:57 UTC (rev 1444)
@@ -2828,7 +2828,7 @@
     	</BugPattern>
     	
 	<BugPattern type="MDM_RUNTIME_EXIT_OR_HALT">
-		<ShortDescription>Method calls {2}</ShortDescription>
+		<ShortDescription>Method calls Runtime.exit() or Runtime.halt()</ShortDescription>
 		<LongDescription>Method {1} calls {2}</LongDescription>
 		<Details>
 		  <![CDATA[
@@ -2838,11 +2838,11 @@
 	</BugPattern>
 
 	<BugPattern type="MDM_RUNFINALIZATION">
-		<ShortDescription>Method calls {2}</ShortDescription>
-		<LongDescription>Method {1} calls {2}</LongDescription>
+		<ShortDescription>Method triggers finalization</ShortDescription>
+		<LongDescription>Method {1} triggers finalization when calling {2}</LongDescription>
 		<Details>
 		<![CDATA[
-		<p>Triggering finalization can result in serious performance problems and may indicate incorrect resource cleanup.</p>
+		<p>Manually triggering finalization can result in serious performance problems and may be masking resource cleanup bugs.</p>
 		]]>
 		</Details>
 	</BugPattern>
@@ -2898,18 +2898,18 @@
 	</BugPattern>
 
 	<BugPattern type="MDM_THREAD_PRIORITIES">
-		<ShortDescription>Method calls non-portable method {2}</ShortDescription>
-		<LongDescription>Method {1} calls non-portable method {2}</LongDescription>
+		<ShortDescription>Method uses suspicious thread priorities</ShortDescription>
+		<LongDescription>Method {1} uses suspicious thread priorities by calling method {2}</LongDescription>
 		<Details>
 		  <![CDATA[
-		  <p>Getting or setting thread priorities is not portable and could indicate race conditions.</p>
+		  <p>Getting or setting thread priorities is not portable and could cause or mask race conditions.</p>
 		  ]]>
 		</Details>
 	</BugPattern>
 
 	<BugPattern type="MDM_THREAD_YIELD">
-		<ShortDescription>Method calls non-portable method {2}</ShortDescription>
-		<LongDescription>Method {1} calls non-portable method {2}</LongDescription>
+		<ShortDescription>Method attempts to manually schedule threads</ShortDescription>
+		<LongDescription>Method {1} attempts to manually schedule threads by calling method {2}</LongDescription>
 		<Details>
 		  <![CDATA[
 		  <p>Manual thread scheduling with <code>Thread.sleep()</code> or <code>Thread.yield()</code> has no guaranteed semantics and is often used to mask race conditions.</p>
@@ -2919,7 +2919,7 @@
 	  
 	<BugPattern type="MDM_WAIT_WITHOUT_TIMEOUT">
 		<ShortDescription>Method sleeps without timeout</ShortDescription>
-		<LongDescription>Method {1} calls {2} without timeout</LongDescription>
+		<LongDescription>Method {1} sleeps without timeout when calling {2}</LongDescription>
 		<Details>
 		  <![CDATA[
 		  <p>Calling <code>{2}</code> without timeout could block forever. Consider using a timeout to detect deadlocks or performance problems. Thread.join() Object.wait() Condition.await() Lock.lock() Lock.lockInterruptibly()</p>
@@ -2928,7 +2928,7 @@
 	</BugPattern>
 		  
 	<BugPattern type="MDM_THREAD_FAIRNESS">
-		<ShortDescription>Method ignores Lock's fairness settings by calling {2}</ShortDescription>
+		<ShortDescription>Method ignores Lock's fairness settings by calling tryLock()</ShortDescription>
 		<LongDescription>Method {1} ignores Lock's fairness settings by calling {2}</LongDescription>
 		<Details>
 		  <![CDATA[
@@ -2949,7 +2949,7 @@
 
 	<BugPattern type="MDM_LOCK_ISLOCKED">
 		<ShortDescription>Method tests if a lock is locked</ShortDescription>
-		<LongDescription>Method {1} calls {2} to test if the lock is locked</LongDescription>
+		<LongDescription>Method {1} tests if a lock is locked by calling {2}</LongDescription>
 		<Details>
 		  <![CDATA[
 		  <p>Calling <code>ReentrantLock.isLocked()</code> or <code>ReentrantLock.isHeldByCurrentThread()</code> might indicate race conditions or incorrect locking. These methods are designed for use in debug code or monitoring of the system state, not for synchronization control.</p>
@@ -2958,7 +2958,7 @@
 	</BugPattern>
 		  
 	<BugPattern type="MDM_STRING_BYTES_ENCODING">
-		<ShortDescription>Encoding String bytes without specifying the character encoding</ShortDescription>
+		<ShortDescription>Method encodes String bytes without specifying the character encoding</ShortDescription>
 		<LongDescription>Method {1} encodes String bytes without specifying the character encoding</LongDescription>
 		<Details>
 		  <![CDATA[
@@ -3069,4 +3069,4 @@
     	<BugCode abbrev="NFF">Non Functional Field</BugCode>
     	<BugCode abbrev="WNG">Wrong Null Guard</BugCode>
     	<BugCode abbrev="MDM">More Dumb Methods</BugCode>
-</MessageCollection>
\ No newline at end of file
+</MessageCollection>


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.