commit 90511e17dcb663076403094b307130a24d698603
author Luis Fernando Pino Duque <lpino@google.com> Thu Jan 28 10:49:58 2016 +0000
committer Kristina Chodorow <kchodorow@google.com> Thu Jan 28 15:30:18 2016 +0000
tree d626d60179c21229e00e788cb3265868a2f6b4fb
parent e70a3376668a3a46e068a97e7b691a064fa23944

Inject the TOOLS_REPOSITORY constant in the RuleClassProvider instead of using Constants.java

It also includes one example on how to use the new mechanism in BazelCppRuleClasses.

This is the first phase for the removal of the TOOLS_REPOSITORY constant.

--
MOS_MIGRATED_REVID=113244399

src/main/java/com/google/devtools/build/lib/analysis/RuleDefinitionEnvironment.java

diff --git a/src/main/java/com/google/devtools/build/lib/analysis/RuleDefinitionEnvironment.java b/src/main/java/com/google/devtools/build/lib/analysis/RuleDefinitionEnvironment.java
index 9a4fb6c2..2eab411 100644
--- a/src/main/java/com/google/devtools/build/lib/analysis/RuleDefinitionEnvironment.java
+++ b/src/main/java/com/google/devtools/build/lib/analysis/RuleDefinitionEnvironment.java
@@ -26,4 +26,9 @@
    * Label#parseAbsolute}. Throws a {@link IllegalArgumentException} if the parsing fails.
    */
   Label getLabel(String labelValue);
+
+  /**
+   * Returns the path to the tools repository. It is different for blaze and bazel.
+   */
+  String getToolsRepository();
 }