Fix documentation of --[no]block_for_lock

The help message of this option had the effect inversed. The default
--block_for_lock setting makes the client block waiting for the lock
when needed, and the flag needs to be unset with --noblock_for_lock
to instead exit immediately.

Also rename the dummy noblock_for_lock variable to blockForLock to match
the naming convention. The variable is not used anywhere, as this class
only exists for the help messages.

--
MOS_MIGRATED_REVID=112566287

1 files changed, 3 insertions, 3 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/runtime/BlazeServerStartupOptions.java b/src/main/java/com/google/devtools/build/lib/runtime/BlazeServerStartupOptions.java
index 8f66df6ac1..4a7de87849 100644
--- a/src/main/java/com/google/devtools/build/lib/runtime/BlazeServerStartupOptions.java
+++ b/src/main/java/com/google/devtools/build/lib/runtime/BlazeServerStartupOptions.java
@@ -169,9 +169,9 @@ public class BlazeServerStartupOptions extends OptionsBase {
   @Option(name = "block_for_lock",
       defaultValue = "true", // NOTE: purely decorative!  See class docstring.
       category = "server startup",
-      help = "If set, Blaze will exit immediately instead of waiting for other " +
-             "Blaze commands holding the server lock to complete.")
-  public boolean noblock_for_lock;
+      help = "If unset with --noblock_for_lock, Blaze will exit immediately instead of "
+            + "waiting for other Blaze commands holding the server lock to complete.")
+  public boolean blockForLock;
 
   @Option(name = "io_nice_level",
       defaultValue = "-1",  // NOTE: purely decorative!