From 1e3f810f8fd8072e098aee06f6148d279ee32b3b Mon Sep 17 00:00:00 2001 From: Joey Perrott Date: Tue, 29 Sep 2020 08:13:47 -0700 Subject: [PATCH] fix(bazel): clean up outstanding failure message for usages of --define=compile (#39046) Removes the failure message put in place to catch usages of the old --define=compile method of setting which compiler was to be used. PR Close #39046 --- packages/bazel/src/ng_module.bzl | 8 -------- 1 file changed, 8 deletions(-) diff --git a/packages/bazel/src/ng_module.bzl b/packages/bazel/src/ng_module.bzl index fc67d73766..f51ca51bad 100644 --- a/packages/bazel/src/ng_module.bzl +++ b/packages/bazel/src/ng_module.bzl @@ -47,14 +47,6 @@ def is_ivy_enabled(ctx): ctx.attr._renderer[BuildSettingInfo].value == "ivy")): return True - # TODO(josephperott): Remove after ~Feb 2020, to allow local script migrations - if "compile" in ctx.var and ctx.workspace_name == "angular": - fail( - msg = "Setting ViewEngine/Ivy using --define=compile is deprecated, please use " + - "--config=ivy or --config=view-engine instead.", - attr = "ng_module", - ) - # This attribute is only defined in google's private ng_module rule and not # available externally. For external users, this is effectively a no-op. if hasattr(ctx.attr, "ivy") and ctx.attr.ivy == True: