bazel - a fast, scalable, multi-language and extensible build system

	Commit message (Collapse)	Author	Age
*	Add rootpath(s) and execpath(s) functions to template expansion	ulfjack	2017-11-03
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	In addition to the $(location) function, we now also support $(rootpath) and $(execpath) functions. Unfortunately, we have to do this in two places since the Skylark API for expand_location has to continue calling into LocationExpander in order to preserve its semantic contract. Progress on #2475. RELNOTES[NEW]: In addition to $(location), Bazel now also supports $(rootpath) to obtain the root-relative path (i.e., for runfiles locations), and $(execpath) to obtain the exec path (i.e., for build-time locations) PiperOrigin-RevId: 174454119
*	Extend from an abstract base class to avoid duplication of utility methods ↵	ruperts	2017-10-18
\| \| \| \| \| \| \|	in RuleErrorConsumers RELNOTES: None. PiperOrigin-RevId: 172387755
*	Extract more RuleContext error-related methods into RuleErrorConsumer	cparsons	2017-10-16
\| \| \| \| \| \| \|	This will make it easier to pass only error-handling functionality into support classes. RELNOTES: None. PiperOrigin-RevId: 172148072
*	Rewrite LocationExpander	ulfjack	2017-10-02
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Split up the functionality into separate classes, and test each independently. (Keep one integration test to make sure it still works together.) This is in preparation for adding another location function for runfiles paths. Currently we have to decide ahead of time whether to expand artifacts as exec paths or root-relative (runfiles) paths, but there are cases where we can't make that decision ahead of time and / or need both to coexist, even in the same attribute. Progress on #2475. PiperOrigin-RevId: 170691666
*	Update LocationExpander to properly handle spaces in filenames.	John Cater	2017-08-01
	Also added basic tests. Change-Id: I5861816bf116486e0ee365debd3dfbda131047f7 PiperOrigin-RevId: 163764257