| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
Removes ResourceMap from AndroidDataSet, now the merge operates directly on the AndroidDataSet instances.
Change tests to use Map<DataKey, Data?> instead of List<Data?>.
Add tests for finding conflicts during AndroidDataSet creation.
Make MergeConflict more test friendly by sorting Paths on creation.
--
MOS_MIGRATED_REVID=118240635
|
|
|
|
|
|
|
|
| |
Removes the remaining IO from Resolver, which is now only responsible for
rule dependency logic.
--
MOS_MIGRATED_REVID=118240098
|
|
|
|
|
|
|
| |
can trigger on it.
--
MOS_MIGRATED_REVID=118234431
|
|
|
|
|
|
|
| |
Making the other classes much more testable!
--
MOS_MIGRATED_REVID=118203206
|
|
|
|
|
|
|
|
|
| |
FileStateValues for output files can make their way into the Skyframe graph if a source file is symlink to an output file.
Also fix a bug where ExternalFilesHelper#isExternalFileSeen would always return true after returning true once in the past. This meant if an external file ever made its way into the Skyframe graph, we would always do a full graph scan at the beginning of each build (iow, we would always waste some CPU time doing nothing interesting).
--
MOS_MIGRATED_REVID=118190190
|
|
|
|
|
|
|
|
|
|
|
| |
This moves logic out of the Java repository function and closer to where it's
actually used, while also downplaying the basic templating a bit and allowing
the logic to interact better with the build file.
The existing logic regarding Apache's HTTP client is migrated as part of this.
--
MOS_MIGRATED_REVID=118084016
|
|
|
|
|
|
|
|
|
| |
and storyboards.
RELNOTES:
--
MOS_MIGRATED_REVID=118077315
|
|
|
|
|
|
|
|
|
| |
The end goal is to remove ResourceMap and separate the DataKey from the DataResource and DataAsset.
This moves the resource map to AndroidDataSet and switches the generation to the Resource and Asset visitors. Which is nice, because it removes a traversal of the overwritable resources and assets.
--
MOS_MIGRATED_REVID=118071238
|
|
|
|
|
|
|
| |
Adds support for parsing and merging assets. This introduces the DataKey and DataAsset interfaces which allow reuse of the FileDataResource for assets, the RelativeAssetPath which acts as a DataKey for assets (the relative asset path is the path that the asset will reside inside the final apk.) It also extends the AndroidDataSetBuilder to handle the creation of assets, and cleans up the interface a little.
--
MOS_MIGRATED_REVID=118060379
|
|
|
|
|
|
|
| |
Fixes #545.
--
MOS_MIGRATED_REVID=118059971
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118049325
|
|
|
|
|
|
|
|
| |
This was causing javacopts containing '=' to be escaped, which makes them
invisible to the underlying javac invocation.
--
MOS_MIGRATED_REVID=118048317
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch replaces the usage of hardcoded "Blaze" string by
Constants.PRODUCT_NAME, so when presenting the output to the user
in the open source version, it says "Bazel" instead of "Blaze",
as "Blaze" is the internal name of the tool and "Bazel" the public
one.
Closes #842
--
Change-Id: I2917656d5254fe34b2761d6e2c79deef7c7fb8a5
Reviewed-on: https://bazel-review.googlesource.com/c/3103/
MOS_MIGRATED_REVID=118042541
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118042058
|
|
|
|
|
|
|
| |
Fixes #1043
--
MOS_MIGRATED_REVID=118039426
|
|
|
|
|
|
|
|
|
|
|
| |
repository.download function now creates the necessary directories before
downloading.
Fixes #1069
Fixes #1078
--
MOS_MIGRATED_REVID=118026986
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118026638
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will tell the experimental UI not to produce updates on the
build status and also pass through correctly STDOUT/STDERR events.
In particular, the standard output is suitable for consumption by
other tools.
--
Change-Id: Ifffd445433a29df20f062a762fe6280229319196
Reviewed-on: https://bazel-review.googlesource.com/#/c/3123
MOS_MIGRATED_REVID=118024251
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118019851
|
|
|
|
|
|
|
| |
RELNOTES: Add ProductType for watch OS 1 extension and application.
--
MOS_MIGRATED_REVID=118003005
|
|
|
|
|
|
|
|
|
| |
This both starts to clean up the code (making it clearer which platform each action is targeted to, caller by caller), as well as allows callers to issue
certain actions for platforms which are not implicitly ios.
We'll still need to migrate callers onto the new method signature.
--
MOS_MIGRATED_REVID=117982741
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117974145
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117968196
|
|
|
|
|
|
|
| |
that keeps the Strings and creates the corresponding Value objects only at expansion time.
--
MOS_MIGRATED_REVID=117947058
|
|
|
|
|
|
|
| |
value 90. When --experimental_oom_more_eagerly is enabled, if after two full GCs the old gen is still >=--experimental_oom_more_eagerly_threshold% full, exit the JVM.
--
MOS_MIGRATED_REVID=117943361
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117939121
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the experimental UI, during build, STDOUT and STDERR events
are reported as separate events, properly terminated by CR LF.
After the completion of the build, however, STDOUT and STDERR
are passed through byte by byte, to allow nicely formatted output.
Info commands, however, do not build, so there is no event to signal
end of build; hence report that fact directly to the UI.
--
Change-Id: Ic236d33ee6e65637016370e15ed37e3d9494a258
Reviewed-on: https://bazel-review.googlesource.com/#/c/3122
MOS_MIGRATED_REVID=117934742
|
|
|
|
|
|
|
|
| |
The previous implementation was hiding errors from before a load
statement as a result of the workspace split.
--
MOS_MIGRATED_REVID=117933781
|
|
|
|
|
|
|
| |
They are automatically added when printing the error message.
--
MOS_MIGRATED_REVID=117927312
|
|
|
|
|
|
|
|
|
|
|
|
| |
If bazel is invoked with --color=no, two event handlers are in use
simultaneously, using different output streams. For the event bus,
register the one that is aware of ansi control characters, as this
is the one that will also pass through stdout/stderr events.
--
Change-Id: I83f1164b9057cebf9345c315f42c8d54a88d3888
Reviewed-on: https://bazel-review.googlesource.com/#/c/3121
MOS_MIGRATED_REVID=117922780
|
|
|
|
|
|
|
| |
action.
--
MOS_MIGRATED_REVID=117915931
|
|
|
|
|
|
|
|
| |
This is one of the last pieces of state in BlazeRuntime that isn't safe to
share across command invocations.
--
MOS_MIGRATED_REVID=117910631
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117894693
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Certain annotation processors that generate references to transitive
dependencies are exempt from Strict Java Deps.
Dagger ensures that all references to transitive types are reachable via a
chain of direct dependencies specified in @Component interfaces. We don't
record dependencies inside dagger-generated code, since Dagger is already
enforcing strict dependencies. By not recording the deps we allow dependency
management tools to remove depednencies that are only needed transitively by
dagger.
This approach doesn't work in general, since processors may generate references
to transitive types that are not reachable via a chain of direct deps, and
which may be subject to pruning by the reduced classpath optimization.
This change causes strict deps to record dependencies (but not emit strict deps
errors) inside code generated by exempt annotation processors other than
Dagger.
--
MOS_MIGRATED_REVID=117882599
|
|
|
|
|
|
|
|
|
| |
xcode_version rule.
--{tvos,watchos,macosx}_sdk_version flags may be used to override defaults specified in these attributes.
--
MOS_MIGRATED_REVID=117869146
|
|
|
|
|
|
|
| |
accidentally keep references to them after the analysis phase.
--
MOS_MIGRATED_REVID=117855145
|
|
|
|
|
|
|
| |
information required for creating a release bundle.
--
MOS_MIGRATED_REVID=117843546
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117841917
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The client provides information about whether the terminal is a tty, and
which width the output should be formatted for. Passing this information
as explicit command-line arguments has the disadvantage that it overrides
any setting in configuration files. While usually there is no one-size-fits-all
value for terminal width, it doesn't make sense either to have an option
where the user cannot set a default. Fix this by providing the client options
as least imported rc-source.
--
Change-Id: Iad9eddbb3ff1777f4b423053e21aeac9fd7c466f
Reviewed-on: https://bazel-review.googlesource.com/#/c/3092
MOS_MIGRATED_REVID=117833645
|
|
|
|
| |
MOS_MIGRATED_REVID=117827486
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117821922
|
|
|
|
|
|
|
|
|
|
|
| |
When specifying which command names to parse options for, given the
command annotation, ensure that "common" comes first, so that it can
be overridden by more specific options.
--
Change-Id: I20cd90c098e993580c32297d1e36c8a6c939873a
Reviewed-on: https://bazel-review.googlesource.com/#/c/3091
MOS_MIGRATED_REVID=117821257
|
|
|
|
|
|
|
|
|
| |
Windows.
Progress towards #930.
--
MOS_MIGRATED_REVID=117799006
|
|
|
|
|
|
|
| |
CustomMultiArgv class.
--
MOS_MIGRATED_REVID=117761242
|
|
|
|
|
|
|
| |
rule, as these protos have already been generated and linked in the released static library.
--
MOS_MIGRATED_REVID=117747156
|
|
|
|
|
|
|
| |
it. The copying showed up as a source of memory spikiness.
--
MOS_MIGRATED_REVID=117741939
|
|
|
|
|
|
|
|
|
| |
the outputs are up-to date as blaze does this for us.
RELNOTES: ProGuard relies on bazel to check to see if the inputs have changed.
--
MOS_MIGRATED_REVID=117736709
|
|
|
|
|
|
|
|
| |
RELNOTES[NEW]: --extra_entitlements allows passing additional entitlements for
iOS signing
--
MOS_MIGRATED_REVID=117735783
|
|
|
|
|
|
|
|
|
| |
Use -p when mkdir, create the server directory in the
temporary directory and ensure we delete the server directory
on the tear_down.
--
MOS_MIGRATED_REVID=117728350
|
|
|
|
|
|
|
| |
the list of files to mount, but was deleted by the time the namespace-sandbox actually mounted the files, it would crash with a "file not found" error.
--
MOS_MIGRATED_REVID=117726198
|