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

	Commit message (Collapse)	Author	Age
*	Remove categories from Bazel options.	ccalvarin	2018-03-28
\| \| \| \| \| \| \| \| \|	These have all had a chance to be categorized with the OptionDocumentationCategory enum, and the help output already uses the enum-grouped format. The "incompatible changes" category has meaning for --all_incompatible_changes and will be removed separately. RELNOTES: None. PiperOrigin-RevId: 190773778
*	Implement --(no)expand_test_suites flag.	dslomov	2017-12-13
\| \| \| \| \| \| \| \| \|	--noexpand_test_suites flag will suppress expansion of test_suite targets into constituent tests, so that command-line aspects can analyze test_suite targets. RELNOTES: Added --(no)expand_test_suites flag. PiperOrigin-RevId: 178892829
*	Minor fixes to spacing in help messages	Mike Morearty	2017-11-29
\| \| \| \| \| \| \| \|	A few help messages were missing a space after the period at the end of a sentence. Closes #4094. PiperOrigin-RevId: 177282132
*	Enable experimental UI by default.	twerth	2017-10-18
\| \| \| \| \|	RELNOTES: Enable experimental UI by default. PiperOrigin-RevId: 172432464
*	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
*	Fold OptionUsageRestrictions into OptionDocumentationCategory and ↵	ccalvarin	2017-07-11
\| \| \| \| \| \| \| \| \| \|	OptionMetadataTags. These are similar, no need to have both fields. Removing the "DOCUMENTED" default, the absence of UNDOCUMENTED will be used instead. Since requiring a documentation category for undocumented options doesn't make sense, list that as one of the OptionDocumentationCategories, but list HIDDEN and INTERNAL as part of OptionMetadata. These options should list UNDOCUMENTED as their category. PiperOrigin-RevId: 161515674
*	Add the default category and tag to all options.	ccalvarin	2017-06-28
\| \| \| \| \| \| \| \|	Move the default from the annotation to every mention. This makes the incompleteness explicit. Will add the defaults to test targets in a separate change. Once all dependencies are cleaned up, the Option annotation will no longer allow options without the documentationCategory or effectTag, to prevent new options being added without categories while we migrate to the new option categorization. PiperOrigin-RevId: 160281252
*	experimental_skyframe_target_pattern_evaluator: Use UNDOCUMENTED instead of ↵	philwo	2017-06-09
\| \| \| \| \| \|	HIDDEN. PiperOrigin-RevId: 158524495
*	Split out option usage restriction from option category.	ccalvarin	2017-04-18
\| \| \| \| \| \| \| \| \|	These are two different concepts. Do not remove category overload compatibility in this CL, to keep this change limited to converting the current uses of category. With some flyby formatting fixes on affected OptionsBases. RELNOTES: None. PiperOrigin-RevId: 153390002
*	Add "--build_manual_tests" options that forces manual tests to be built.	dslomov	2017-04-04
\| \| \| \| \| \| \| \| \|	This is useful for IDEs and other tools utilizing command-line aspects for reflection over build graph. RELNOTES: None. PiperOrigin-RevId: 152038248
*	Run the analysis phase with as many threads as the user wants. In order to ↵	Janak Ramakrishnan	2016-11-18
\| \| \| \| \| \| \| \| \|	avoid memory blow-up intra-configured-target analysis, use a semaphore to ensure that CPU-bound work only occurs on #CPU-many threads. RELNOTES: Use --loading_phase_threads to control the number of threads used during the loading/analysis phase. -- MOS_MIGRATED_REVID=139477645
*	Implement build tag filtering.	Lukacs Berki	2016-11-11
\| \| \| \| \| \| \|	If the --build_tag_filters option is specified, targets built will be filtered according to their tags (at least one included, none excluded) -- MOS_MIGRATED_REVID=138856195
*	Fix the --loading_phase_threads to work during "blaze build". Previously and ↵	Eric Fellheimer	2016-02-23
\| \| \| \| \| \| \|	confusingly it only worked on "blaze query". -- MOS_MIGRATED_REVID=115338436
*	Add an experimental flag to enable the Skyframe-based loading phase runner.	Ulf Adams	2016-02-12
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	Refactor the CommandEnvironment to no longer create a LoadingPhaseRunner eagerly. Unfortunately, that means we can't reuse the TargetPatternEvaluator either. Fortunately, the SkyframeTargetPatternEvaluator is a very lightweight class, which only contains the offset as state, so we just create a new instance whenever we need one. On the plus side, the LoadingPhaseRunner API is now stateless, and the QueryCommand no longer creates a unnecessary LoadingPhaseRunner instance. -- MOS_MIGRATED_REVID=114519731
*	Move LoadingPhaseRunner.Options to top-level class LoadingOptions.	Ulf Adams	2015-11-02
	-- MOS_MIGRATED_REVID=106836859