| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 187551970
|
|
|
|
|
|
|
| |
fix logic for implementing emulated interfaces.
RELNOTES: None.
PiperOrigin-RevId: 187520298
|
|
|
|
|
|
| |
RELNOTES:
Removed flag `--incompatible_load_argument_is_label`.
PiperOrigin-RevId: 187479614
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Implement a manifest-based Runfiles object, add
tests and test utils (MockFile).
Subsequent commits will add more feataures:
- creating list of envvars to pass to child
processes
- automatic Runfiles creation based on argv[0] and
the envvars of this process
See https://github.com/bazelbuild/bazel/issues/4460
Change-Id: I4376ede3ac00241688ff16a36ed596fb08f13a72
PiperOrigin-RevId: 187318502
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 187239449
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 187185374
|
|
|
|
|
|
|
|
| |
flags by it.
RELNOTES: None.
PiperOrigin-RevId: 187075897
|
|
|
|
|
|
|
| |
This zip is the input to the resource shrinker, which currently sometimes chokes on databinding expressions. This should fix that.
RELNOTES: None
PiperOrigin-RevId: 187049578
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Implement the foundation of the C++ runfiles
library, along with a directory-based Runfiles
implementation.
Subsequent commits will add more feataures:
- manifest-based runfiles handling
- creating list of envvars to pass to child
processes
- automatic Runfiles creation based on argv[0] and
the envvars of this process
See https://github.com/bazelbuild/bazel/issues/4460
Change-Id: Id5a38619a1ae874499f04523863081559360410c
PiperOrigin-RevId: 187031518
|
|
|
|
|
|
|
| |
See https://github.com/bazelbuild/bazel/issues/4614 and https://github.com/bazelbuild/bazel/commit/bcefd9833cb5620fef8a27c37c2808a66b57c7e6.
RELNOTES: None
PiperOrigin-RevId: 187029042
|
|
|
|
|
|
|
|
| |
If `argument` does not contain `' '` and `'"'` and `escape_backslash` is false (i.e: no escaping needed), `escaped_arg` will allocate memory exactly once only.
Closes #4491.
PiperOrigin-RevId: 186962716
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 186904092
|
|
|
|
|
|
|
| |
reporting that there is a missing 'Args:' section.
RELNOTES: None.
PiperOrigin-RevId: 186717757
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 186693205
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 186690865
|
|
|
|
|
|
|
|
| |
being desugared.
RELNOTES: None.
PiperOrigin-RevId: 186675372
|
|
|
|
|
|
|
|
|
| |
Because of limitations in Bazel (primarily, Filesets), we always need to filter
on density in execution. As such, remove the deprecated flag that was used to
specify densities that were stamped but not filtered.
RELNOTES: none
PiperOrigin-RevId: 186634496
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 186565673
|
|
|
|
|
|
|
|
| |
invokespecial invocations for core interfaces.
RELNOTES: None.
PiperOrigin-RevId: 186404206
|
|
|
|
|
|
|
|
| |
corresponding Proguard-style -keep rules
RELNOTES: None.
PiperOrigin-RevId: 186372769
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 186297559
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Unclassified general breakages in tests. Rolling back for further investigation.
*** Original change description ***
Normalized the serialization proto to save space and allow greater versatility in storage.
RELNOTES: None
PiperOrigin-RevId: 186057879
|
|
|
|
|
|
|
| |
versatility in storage.
RELNOTES: None
PiperOrigin-RevId: 186036607
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We run ResourceCompiler#visitFile once per resource file being compiled. If the
file has qualifiers aapt2 doesn't support (es-419 or sr-latn), we copy the file
into a new directory with corrected qualifiers. However, Files.createDirectory
fails if the folder already exists (because, for example, we just copied
another file).
Instead, use Files.createDirectories, which allows the folder to already exist.
RELNOTES: none
PiperOrigin-RevId: 185887192
|
|
|
|
|
|
|
|
| |
android desugaring
RELNOTES: None.
PiperOrigin-RevId: 185863194
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 185847904
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add "JAVA_RUNFILES" (and "RUNFILES_DIR") to the
dict that Runfiles.EnvVars() returns in the Python
runfiles library, so Python programs that use the
Python runfiles library in @bazel_tools can now
run java_binary data-dependencies as subprocesses
and the latter will find the runfiles.
See https://github.com/bazelbuild/bazel/issues/4460
Change-Id: I0566f6d3c68631a1d99e67964fbe8019ee82324b
PiperOrigin-RevId: 185812948
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Windows native {java,py,sh}_binary launcher
now picks up the RUNFILES_MANIFEST_FILE and
RUNFILES_DIR envvars from the environment. This
enables running such binaries even when they are
data-dependencies of other binaries and thus have
no runfiles (manifest or directory) of their own.
See https://github.com/bazelbuild/bazel/issues/4460
Change-Id: I1bc8e30f81b9932ea7c96ded2717ac9d0600403d
PiperOrigin-RevId: 185656004
|
|
|
|
|
|
|
|
|
|
| |
We can now compile
//src/tools/singlejar:token_stream on Windows.
See https://github.com/bazelbuild/bazel/issues/2241
Change-Id: I98f86e608e5ebaf685e4de26b2dabe75fcca78d2
PiperOrigin-RevId: 185655986
|
|
|
|
|
|
|
|
|
|
|
|
| |
I neglected to unify the message text before submit. This uses the Go version
for both go and Java.
R=laurentlb,mkanat
CC=blaze-firehose+cl
RELNOTES:
unifly lint glob(["**/*.java"]) message
PiperOrigin-RevId: 185569422
|
|
|
|
|
| |
RELNOTES:None
PiperOrigin-RevId: 185553306
|
|
|
|
|
|
|
|
|
|
|
| |
ControlFlowChecker has a precondition check that assumes nested functions do not occur. While this assumption is reasonable for a valid Skylark syntax, linter can actually be invoked on malformed files and users would get a stack trace instead of a human-readable linter error.
Alternative and possibly a better strategy would to not run CFChecker in case parse errors are detected.
fixes #4511
Closes #4512.
PiperOrigin-RevId: 185538897
|
|
|
|
|
|
|
| |
try-with-resources code segments
RELNOTES:None
PiperOrigin-RevId: 185536875
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 185535264
|
|
|
|
|
|
|
|
|
| |
For now we will only block Java recursive globs. Any other languages or
extensions can be banned relatively easily.
RELNOTES:
Add lint check for discouraging glob(["**/*.java"])
PiperOrigin-RevId: 185417760
|
|
|
|
|
|
|
|
| |
- make Objects.requireNonNull and Long.compare rewrites compatible with --core_library
- apply those and try-with-resources rewrites to generated companion classes
RELNOTES: None.
PiperOrigin-RevId: 185262256
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 185218745
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rename the runfiles library's Runfiles.EnvVar()
method to EnvVars(), indicating that it may return
multiple entries in the dict.
In the future this method will return multiple
keys, but I want to update the interface ASAP so
that it is stable after it's released in Bazel
0.12.0.
See https://github.com/bazelbuild/bazel/issues/4460
Change-Id: I8ab3a2a64736ff746dd96fea80ba2f5356dcfcc3
PiperOrigin-RevId: 185118832
|
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 185082719
|
|
|
|
|
| |
RELNOTES:none
PiperOrigin-RevId: 185027580
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Python runfiles library will no longer pick up
the runfiles directory from $TEST_SRCDIR.
This is in accordance with the Java runfiles
library, see the motivation in
https://github.com/bazelbuild/bazel/issues/4598
The commit also adds a test for this functionality
as well as exercising that the runfiles library
can find the runfiles directory even if no
RUNFILES_* envvars are exported.
See https://github.com/bazelbuild/bazel/issues/4598
See https://github.com/bazelbuild/bazel/issues/4460
Change-Id: I6e4d154cdca66b29d7c6e77743cf8109638238b5
PiperOrigin-RevId: 185009819
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bazel 0.11.0 releases a new Java runfiles library
in @bazel_tools. This commit fixes some bugs in
0.11.0rc1:
- The library no longer respects TEST_SRCDIR, so
now it's possible to run Bazel inside of a test
and build and run a mock java_binary, and that
java_binary will *not* pick up the test's
TEST_SRCDIR.
- The library now allows calling rlocation for
absolute paths, and just returns the path
itself. This is in accordance with how our Bash
rlocation() implementation works.
Change-Id: I471247d7538a76ea8162d2192add3f9733f844a8
PiperOrigin-RevId: 184990272
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 184915177
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 184869773
|
|
|
|
|
|
|
|
| |
https://bugs.openjdk.java.net/browse/JDK-8066981
RELNOTES: None.
PiperOrigin-RevId: 184732576
|
|
|
|
|
|
|
|
|
|
|
|
| |
Filtering only in analysis was neglecting the possibility of resources being in
filesets, the contents of which are not available in analysis. As such, we must
*always* filter in execution, even though it's usually just going to be a
no-op.
Also, add some documentation of same.
RELNOTES: none
PiperOrigin-RevId: 184722564
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 184667932
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 184619885
|
|
|
|
|
|
| |
Closes #4489.
PiperOrigin-RevId: 184532916
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also update the Python stub script template to set
$RUNFILES_MANIFEST_FILE or $RUNFILES_DIR so the
runfiles library only needs to look for those.
See https://github.com/bazelbuild/bazel/issues/4460
RELNOTES[NEW]: python,runfiles: You can now depend on `@bazel_tools//tools/runfiles:py-runfiles` to get a platform-independent runfiles library for Python. See DocString of https://github.com/bazelbuild/bazel/blob/master/src/tools/runfiles/runfiles.py for usage information.
Change-Id: I4f68a11cb59f2782e5203e39fe60cc66b46023a2
PiperOrigin-RevId: 184515490
|