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

	Commit message (Collapse)	Author	Age
*	Rename Transition to ConfigurationTransition.	gregce	2018-01-30
\| \| \| \|	PiperOrigin-RevId: 183859414
*	Move PatchTransition and kin to analysis.config.transitions.	gregce	2018-01-04
\| \| \| \| \| \| \|	HostTransition can't be migrated yet because it depends on BuildConfiguration. PiperOrigin-RevId: 180842784
*	Replace Attribute.Transition with config.transitions.Transition.	gregce	2017-12-22
\| \| \| \|	PiperOrigin-RevId: 179936355
*	android_test binary_under_test/deps must have the same flags if any are set.	mstaib	2017-08-31
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	After this CL, if the feature_flags attribute of android_test or android_binary is not set, no transition takes place when entering that rule. This means that if it is depended upon by another test or binary, it will use the enclosing test or binary's flags. This permits users of feature flags to depend on non-users of feature flags. The opposite is still not permitted. If a dep sets feature flags, then the target depending on it must have the exact same feature flags set. This way, all targets used in an android_test are built the same way, but it's possible to interoperate with targets which are agnostic to feature flags. Note that "not set" is different from "set to the empty dictionary"; the former reuses the definitions set higher up in the build graph, while the latter clears all feature flag values and resets them to their defaults. RELNOTES: None. PiperOrigin-RevId: 167035122
*	Replace Transitions.configurationHook with equivalent rule class transitions.	gregce	2017-07-07
	This removes the last dynamic dependency on the static configuration transition table. PiperOrigin-RevId: 161162272