| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
All options need to explicitly list their category and effect. If they are uncategorized, this makes the lack of information obvious. Remove defaults from the annotation to enforce this.
Also enforce the sanity check that no option should have UNKNOWN or NO_OP effects listed with other effect tags.
Includes some last default sets for options I missed in the previous mass-setting change, and some that were added since.
PiperOrigin-RevId: 160641861
|
|
|
|
|
|
|
|
| |
This target include all non tests targets of Bazel to do integration tests of
bootstrapping.
--
MOS_MIGRATED_REVID=115830741
|
|
|
|
|
|
|
|
| |
While doing this, homogenize the two dependencies on build.proto (via
build_proto and build_proto_v2) into a single build_java_proto.
--
MOS_MIGRATED_REVID=115328219
|
|
|
|
|
|
|
|
|
| |
to plmerge.
As of this change plmerge can consume either a protobuf or command line arguments. Once bazel uses plmerge strictly with protobufs, the command line arguments will be deprecated.
--
MOS_MIGRATED_REVID=109716003
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105511114
|
|
It didn't get exported last time for some reasons
--
Change-Id: Ia7fa7bcdd0f06af6c4aa2bc7c26de4b7209f51f7
Reviewed-on: https://bazel-review.googlesource.com/#/c/1450/
MOS_MIGRATED_REVID=95025211
|