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

	Commit message (Collapse)	Author	Age
*	Cleanup of expansion option naming	ccalvarin	2017-09-21
\| \| \| \| \| \| \| \| \|	Options that expand to other options are expansion options and the options they expand to have values that were expansions. This can be a bit confusing. Removes the isExpansion() call that is somewhat ambiguous, and forces option users to explicitly check the option definition for this information. Also provide a parallel boolean function for implicit requirements, so that we stop querying for the length of the implicit requirement all over the place. RELNOTES: None. PiperOrigin-RevId: 169461566
*	Options with oldNames will no longer get reported twice in the effective ↵	ccalvarin	2017-09-11
\| \| \| \| \| \| \| \| \| \|	option lists. Tracking the names together for option identification was useful, but then the same list was being used as the source of options for the parser, which lead to some options being listed twice. Also complete a few tests that should have already been tested in different orders. PiperOrigin-RevId: 168024719
*	Add OptionDefinition layer between the @Option annotation and its fields and ↵	ccalvarin	2017-08-22
\| \| \| \| \| \| \| \| \| \| \|	the options parser. Removes any direct reads of the annotation outside of OptionDefinition. This allows for fewer manual checks for the annotation's existence, unifies error wording, and paves the way for potentially generifying the OptionsParser to accept different @Option-equivalent annotations. Also allows for cleanup of duplicate code by giving @Option-specific operations a clear home, such as sorts and default logic. In followup changes, we can eliminate some unnecessarily complex caching by instead memoizing values in the OptionDefinition. This will have the positive side effect of making sure reads come from the cached values. RELNOTES: None. PiperOrigin-RevId: 166019075
*	Make the @Option annotation depend on the java version of the tagging enums.	ccalvarin	2017-07-18
\| \| \| \| \| \| \|	The option filters proto dependency can be removed from the OptionsParser. This is in response to option parser users that want to avoid the bazel-internal proto file in their dependencies. RELNOTES: None. PiperOrigin-RevId: 162249778
*	Allow expansion flags to have values.	Googler	2017-06-28
\| \| \| \| \| \| \|	This lets us change what it expands based on the argument passed to the flag. RELNOTES: Allows flags that expand to take values. PiperOrigin-RevId: 160298412
*	Update the --incompatible_ flag requirements to use the metadata tag.	ccalvarin	2017-06-28
\| \| \| \| \| \|	Leave the category for now as the generated docs still do not use the new categorization. PiperOrigin-RevId: 160290297
*	Use ImmutableList for Option expansion functions	Googler	2017-06-08
\| \| \| \| \|	RELNOTES: None PiperOrigin-RevId: 158279811
*	Rename some --incompatible_* flags to be more specific	brandjon	2017-05-08
\| \| \| \| \| \| \| \| \|	This is possibly a nit, but we don't want to reuse flag names in the future, so it's a good idea to include what the flag does in the name as opposed to just the feature it affects, in case the same feature is changed multiple times. Updated javadoc for incompatible change system to say so. This rename is ok because these flags have only been submitted over the past couple days. RELNOTES: None PiperOrigin-RevId: 155371363
*	Add --all_incompatible_changes, the user's shorthand for turning on all ↵	brandjon	2017-04-03
	--incompatible_* flags Note that if a developer adds a poorly-formatted incompatible change @Option, constructing an OptionsParser will now fail with an unchecked exception. This can cause some unit tests to fail in unexpected ways, but the developer should see an appropriate error message when the server starts up. To be added: A separate integration test that ensures the expansions of --all_incompatible_changes don't clobber each other. RELNOTES: None PiperOrigin-RevId: 151858287