diff options
| -rw-r--r-- | site/docs/user-manual.html | 8 | ||||
| -rw-r--r-- | src/main/java/com/google/devtools/build/lib/analysis/BuildView.java | 4 |
2 files changed, 2 insertions, 10 deletions
diff --git a/site/docs/user-manual.html b/site/docs/user-manual.html index 33dfcdbcdc..0c4a9b5900 100644 --- a/site/docs/user-manual.html +++ b/site/docs/user-manual.html @@ -1165,14 +1165,6 @@ $ bazel fetch //... </tr> </table> -<h4 id='flag--analysis_warnings_as_errors'><code>--[no]analysis_warnings_as_errors</code></h4> -<p> - When this option is enabled, visible analysis warnings (as specified by - the output filter) are treated as errors, effectively preventing the build - phase from starting. This feature can be used to enable strict builds that - do not allow new warnings to creep into a project. -</p> - <h3 id='flags-options'>Flags options</h3> <p> These options control which options Bazel will pass to other tools. diff --git a/src/main/java/com/google/devtools/build/lib/analysis/BuildView.java b/src/main/java/com/google/devtools/build/lib/analysis/BuildView.java index 4a1bd249f7..04c2096482 100644 --- a/src/main/java/com/google/devtools/build/lib/analysis/BuildView.java +++ b/src/main/java/com/google/devtools/build/lib/analysis/BuildView.java @@ -176,8 +176,8 @@ public class BuildView { + " an upcoming Blaze release", defaultValue = "false", category = "strategy", - documentationCategory = OptionDocumentationCategory.UNCATEGORIZED, - effectTags = {OptionEffectTag.UNKNOWN}, + documentationCategory = OptionDocumentationCategory.UNDOCUMENTED, + effectTags = {OptionEffectTag.NO_OP}, help = "Treat visible analysis warnings as errors." ) public boolean analysisWarningsAsErrors; |