Internal change: Fix compliance regression in from unknown commit
I'm not totally happy with this change. We probably should add a method for mock license support. But this will do to get us on the right track.
The underlying problem is that we have tests which mingle mocks with live rule code. This is fragile. Mock it all, or pull in all of the live things. The first is difficult and may not test reality. The latter forks blaze and bazel tests.
RELNOTES: None
PiperOrigin-RevId: 566922698
Change-Id: I67ffed21240385c73b56133424a01487cdbe9714
diff --git a/src/test/java/com/google/devtools/build/lib/testutil/TestConstants.java b/src/test/java/com/google/devtools/build/lib/testutil/TestConstants.java
index 6e5cbc5..69b11d5 100644
--- a/src/test/java/com/google/devtools/build/lib/testutil/TestConstants.java
+++ b/src/test/java/com/google/devtools/build/lib/testutil/TestConstants.java
@@ -104,6 +104,9 @@
/** The path in which the mock cc crosstool resides. */
public static final String MOCK_CC_CROSSTOOL_PATH = "tools/cpp";
+ /** The path in which the mock license rule resides. */
+ public static final String MOCK_LICENSE_SCRATCH = "third_party/rules_license/";
+
/** The workspace repository label under which built-in tools reside. */
public static final RepositoryName TOOLS_REPOSITORY = RepositoryName.BAZEL_TOOLS;
/** The file path in which to create files so that they end up under {@link #TOOLS_REPOSITORY}. */
