| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
--incompatible_load_argument_is_label enabled (fixes #3560)
Closes #3562.
PiperOrigin-RevId: 167745885
|
|
|
|
|
|
|
|
| |
RELNOTES[INC]:
Keyword-only syntax in a function definition is now forbidden
e.g. `def foo(a, *, b)` or `def foo(a, *b, c)`
PiperOrigin-RevId: 167741296
|
|
|
|
|
|
|
| |
-classobfuscationdisctionry and -packageobfuscationdictionary arguments
RELNOTES: Make proguard_apply_dictionary also apply to class and package obfuscation, not just class members.
PiperOrigin-RevId: 167735831
|
|
|
|
|
|
| |
ToolchainContext.
PiperOrigin-RevId: 167729868
|
|
|
|
|
|
|
|
|
| |
package crosses into a local repository.
Part of #3553.
Change-Id: Ib21de0a1843e72055c53ef34922d69290aee72ed
PiperOrigin-RevId: 167726591
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The RuleClassProvider includes a copy of the product name, parameterized
for both Blaze and Bazel. Apparently, this is exclusively there so that
the standalone docgen binary can "magically" guess the product name.
This is strange and adds additional complexity to the Bazel core codebase
for no strong reason. Instead, just add a new flag to docgen that takes
the product name and pass it in explicitly.
RELNOTES: None.
PiperOrigin-RevId: 167724033
|
|
|
|
| |
PiperOrigin-RevId: 167720760
|
|
|
|
|
|
|
|
|
| |
The resources attribute is being deprecated. Add a flag to disable it so we can
test impact locally and turn it off globally without waiting for a Bazel
release.
RELNOTES: none
PiperOrigin-RevId: 167717822
|
|
|
|
|
|
|
| |
Remove optional variation and simplify node specifications.
Change-Id: Ie0a137768312152d9c036a94e5214b419b3c12ce
PiperOrigin-RevId: 167717139
|
|
|
|
|
| |
Change-Id: If2bf41a96cde21bb97017d4fa35f8f61111635a1
PiperOrigin-RevId: 167714075
|
|
|
|
|
|
|
|
| |
Care is taken so that this is only present when building with Bazel at HEAD
such that Bazel can still be built with its released version.
RELNOTES: None.
PiperOrigin-RevId: 167713922
|
|
|
|
|
|
|
|
|
| |
fixes #3285
kept the existing message in case someone is parsing this text
Closes #3677.
PiperOrigin-RevId: 167707934
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
...or any other non repository rule.
Using a bind rule as the name of the repository was returning
a strange error "could not find handler for bind rule" which was
not useful, so was replaced by a crash.
Fixes #3664
Change-Id: Id0711470e6a1ab9267e05eb273900b18d0a27d6b
PiperOrigin-RevId: 167706825
|
|
|
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/commit/268c0bcbf79f9f3f72d95fa51af0f1b18c5ce29e
Fixes #3693
RELNOTES: None.
PiperOrigin-RevId: 167704700
|
|
|
|
|
|
|
|
|
| |
Split collect, concurrent, vfs, windows into package-level BUILD files.
Move clock classes out of "util", into their own Java package.
Move CompactHashSet into its own Java package to break a dependency cycle.
Give nestedset and inmemoryfs their own package-level BUILD files.
PiperOrigin-RevId: 167702127
|
|
|
|
| |
PiperOrigin-RevId: 167699728
|
|
|
|
|
|
| |
Fixes #3626.
PiperOrigin-RevId: 167687039
|
|
|
|
| |
Change-Id: Id63d774cf9f5ce0a33ffc926f4160831e78aeba2
|
|
|
|
|
|
|
| |
android_sdk_repository and android_ndk_repository without api_level.
RELNOTES: None
PiperOrigin-RevId: 167655738
|
|
|
|
|
|
|
| |
This was displayed to the user during the build, which could result in a lot of extra log data.
RELNOTES: None.
PiperOrigin-RevId: 167641446
|
|
|
|
|
|
|
| |
organize the output tree of android_binary.
RELNOTES: None.
PiperOrigin-RevId: 167630660
|
|
|
|
|
|
| |
RELNOTES: n/a
PiperOrigin-RevId: 167619442
|
|
|
|
|
|
|
|
|
|
| |
- require_defined_versions is deprecated and a no-op. A version must match existing defined versions if any exist
- default label must be present in versions labels if any are defined
- default label may not exist if no versions are defined
- when --xcode_version is specified on the command line, it must match a defined version if any are defined. If none are defined, this flag is a no-op
RELNOTES: None.
PiperOrigin-RevId: 167616628
|
|
|
|
|
|
| |
AFAICT this is unused, remove before it becomes used.
PiperOrigin-RevId: 167616353
|
|
|
|
|
|
|
| |
Also distinguish between unspecified base arg and base 10, so "int(True, 10)" is now an error. This is an incompatible change, albeit a small one.
RELNOTES: None
PiperOrigin-RevId: 167616143
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 167614625
|
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 167608048
|
|
|
|
|
|
|
|
|
| |
repository.
Part of #3553.
Change-Id: Id8b4958844b2ad7b5ce4b2ea00a91b6b22acc025
PiperOrigin-RevId: 167589110
|
|
|
|
|
|
|
|
|
|
| |
user_compile_flags
Also add magic to a feature named 'unfiltered_compile_flags' so the flags
expanded from it are not subject to nocopt filtering.
RELNOTES: None.
PiperOrigin-RevId: 167587189
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/3672
RELNOTES: None
PiperOrigin-RevId: 167581302
|
|
|
|
|
|
|
|
| |
How expanding flags interact with other possible flag qualities is not defined. Should repeated values have effects multiple times and accumulate? This doesn't really make sense, expansion flags don't have values that would accumulate. For this reason, don't allow expansion options to have allowMultiple set to true.
Likewise for other behaviors.
PiperOrigin-RevId: 167580641
|
|
|
|
|
|
| |
Closes #3640.
PiperOrigin-RevId: 167578762
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 167574104
|
|
|
|
|
|
|
|
|
|
| |
tools/android is no longer part of the SDK, they've switched to
tools/bin/sdkmanager. Furthermore, on Windows it is tools/bin/sdkmanager.bat.
Instead, just check if the sdk directory exists.
RELNOTES: None
PiperOrigin-RevId: 167573133
|
|
|
|
|
|
|
|
| |
#3257
Closes #3627.
PiperOrigin-RevId: 167571696
|
|
|
|
|
|
|
|
|
| |
We no longer need to use the custom rules.
Closes #3598.
Change-Id: Ib746cb06836fc9de9b66e7600644bb02291d0891
PiperOrigin-RevId: 167568605
|
|
|
|
|
|
|
|
| |
for Linux platforms.
Fix discard_graph_edges_test.sh
PiperOrigin-RevId: 167568133
|
|
|
|
|
|
|
|
| |
This is a follow-on to https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/bazel-dev/Q2owiR-e86s/ugrVUhn7AwAJ to introduce more usages of Java 8 idioms and other "cleanups", with the intention of making the code base easier to maintain.
Closes #3623.
PiperOrigin-RevId: 167566256
|
|
|
|
|
|
| |
Closes #3673.
PiperOrigin-RevId: 167558706
|
|
|
|
|
|
|
|
|
| |
Also moves parenthetical remark to a completely different sentence, as
it seemed off where it was.
Closes #3657.
PiperOrigin-RevId: 167558504
|
|
|
|
|
| |
RELNOTES:
PiperOrigin-RevId: 167554617
|
|
|
|
|
|
| |
These are now unused. Users are expected to add command lines directly, using (say) CustomCommandLine.
PiperOrigin-RevId: 167554157
|
|
|
|
|
|
|
| |
Turns out, my previous search expression didn't find the ones that were not "final LOG" or "final log" and a surprising number of places were missing the "final" tag.
RELNOTES: None.
PiperOrigin-RevId: 167547507
|
|
|
|
| |
Change-Id: Ie8b7dfe207f05f69fdd4499c38cb8baefa3d997f
|
|
|
|
|
|
|
| |
Previously, only arguments in parameter file are converted to long path.
Now, we convert every path we use to long path.
Change-Id: Iafff8b7a0f69f82cc9f8f9399b35528814eb7715
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
aar_resources_extractor now supports long paths
on Windows.
If the script needs to extract a file from the
AAR where the destination path is too long, the
script will:
1. create a temporary junction under a short path,
pointing to the destination directory (which
has a long path)
2. extract the file under the junction
3. delete the junction and the temp directory
See https://github.com/bazelbuild/bazel/issues/3659
Change-Id: Ie85665b360a6514afaac546aaec8869224fe9d06
PiperOrigin-RevId: 167545085
|
|
|
|
| |
PiperOrigin-RevId: 167520688
|
|
|
|
|
|
|
| |
This removes our dependency on third_party/joda_time, which can be removed in the next commit.
Change-Id: Ibda131d34d0abdc2d675db4bfbd2e99480c055ee
PiperOrigin-RevId: 167515260
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 167505493
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 167502103
|