Jules Villard e4dd2bbd8c [buck] one buck mode datatype to rule them all ... Summary: This changes how we select amongst our (currently) 4 Buck integrations for Java and clang, as well as how the user's choice is reflected by the Config module. The old command line interface is still supported but is now deprecated. The changes in how to select each integration are: - clang via "flavors", activated with `--flavors`, now with `--buck-clang` - clang via "compilation DB", activated with `--buck-compilation-database`, unchanged - Java via "genrule", activated with `--genrule-master-mode`, now with `--buck-java` - Java "without genrules", used to be activated by *not specifying any other Buck mode*, unchanged Instead of various `Config` flags corresponding to the previous CLI that are allowed in any combination of `flavors`, `buck_compilation_database`, `genrule_master_mode`, `Config` now exposes a single `buck_mode` datatype. This allows, eg, `flavors` to override `buck_compilation_database` if needed. It will also make it easier to get rid of the old "Java without genrules" integration in a later diff (see inline comments). Reviewed By: ngorogiannis Differential Revision: D19175686 fbshipit-source-id: 29b3831be		5 years ago
..
src	[copyright] Remove years	6 years ago
.buckconfig	[tests] add test for Buck flavors integration	8 years ago
.buckversion	[tests] fix buck tests	6 years ago
Makefile	[buck] one buck mode datatype to rule them all	5 years ago
buck_target.txt	[buck integration] Support passing targets by file to buck in both the compilation database integration and the flavors integration	8 years ago
issues.exp	[tests] record error bucket in expected output	7 years ago