Document the startup option --host_javabase.
RELNOTES: Document startup option --host_javabase
@@ -1859,6 +1859,10 @@ The default is <code>armeabi-v7a</code>.
<a href="#flag--java_toolchain"><code class='flag'>--java_toolchain</code></a>
option.
</p>
+<p>
+ This option should not be confused with the startup option
+ <a href='#startup_flag--host_javabase'>--host_javabase</a>.
+</p>
<h3 id='strategy-options'>Build strategy options</h3>
<p>
@@ -3471,6 +3475,22 @@ adb -s deadbeef install ...
base) if there is a better location in your filesystem layout.
</p>
+<h4 id='startup_flag--host_javabase'><code class='flag'>--host_javabase=<var>dir</var></code></h4>
+<p>
+ Specifies the Java virtual machine in which <i>Bazel itself</i> runs. The value must be a path to
+ the directory containing a JDK or JRE. It should not be a label.
+ This option should appear before any bazel command, and not be confused with the build option
+ <a href='#flag--host_javabase'>--host_javabase</a>, for example:
+</p>
+<pre>
+ % bazel --host_javabase=/usr/local/buildtools/java/jdk9 build //foo
+</pre>
+<p>
+ This flag does <i>not</i> affect the JVMs used by Bazel subprocesses such as applications, tests,
+ tools, and so on. Use build options <a href='#flag--javabase'>--javabase</a> or
+ <a href='#flag--host_javabase'>--host_javabase</a> instead.
+</p>
+
<h4 id='flag--host_jvm_args'><code class='flag'>--host_jvm_args=<var>string</var></code></h4>
<p>
Specifies a startup option to be passed to the Java virtual machine in which <i>Bazel itself</i>
