aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/main/java
Commit message (Collapse)AuthorAge
* Fix a bug that causes unnecessary warning "setting 'linkstatic=1' is ↵Gravatar Yuannan Cai2016-11-08
| | | | | | | | | | | recommended if there are no object files", when versioned shared library is in srcs fields like "a.so.2.0". In appearsToHaveObjectFiles(), we take into account SHARED_LIBRARY, but no VERSIONED_SHARED_LIBRARY. Fixes #310 . -- MOS_MIGRATED_REVID=138408789
* Prohibited comparison of Skylark setsGravatar Vladimir Moskva2016-11-08
| | | | | | | RELNOTES: Comparing sets (`if set1 < set2:`) is not allowed anymore in Skylark because it didn't work correctly anyway. -- MOS_MIGRATED_REVID=138408411
* Progress on migrating java_lite_proto_library to Skylark.Gravatar Irina Iancu2016-11-08
| | | | | -- MOS_MIGRATED_REVID=138391269
* Fixed StringIndexOutOfBoundsException in the lexerGravatar Vladimir Moskva2016-11-08
| | | | | -- MOS_MIGRATED_REVID=138387292
* Upload empty files to remote execution. I was too eager to optimize empty filesGravatar Ola Rozenfeld2016-11-08
| | | | | | | | away -- Bazel should still work with remote execution servers that don't have that optimization. -- MOS_MIGRATED_REVID=138384785
* For SpawnActions, also honor the dynamic environmentGravatar Klaus Aehlig2016-11-07
| | | | | | | | | | | | | For SpawnActions, depending on the value of use_default_shell_env, the specified environment is taken. The shell environment, however, consists of two parts: a static mapping of variables to values, and a set of variables where the value is to be taken from the client environment. Make sure, both parts are set correctly. Fixes #2035. -- Change-Id: I32253e9bf651b18ca25107edc5fc839813905726 Reviewed-on: https://bazel-review.googlesource.com/#/c/7211 MOS_MIGRATED_REVID=138376914
* Rollback of commit a396b070ae36032a973672e11145533621c39edc.Gravatar Klaus Aehlig2016-11-07
| | | | | | | | | | | | | | | *** Reason for rollback *** Breaks tests on latest, as proto_lang_toolchain didn't make it into the 0.4.0 release see http://ci.bazel.io/job/bazel-tests/306/BAZEL_VERSION=latest,PLATFORM_NAME=linux-x86_64/console *** Original change description *** Use proto_lang_toolchain() in java_proto_library. -- MOS_MIGRATED_REVID=138372522
* If separate interface and implementation contexts are used, only the interfaceGravatar Googler2016-11-07
| | | | | | | | | | | context should generate a module map and module. This whole code is a bit convoluted and the increasing number of boolean parameters to initializeCppCompilationContext is smelly. I plan to clean this up in a follow-up CL. -- MOS_MIGRATED_REVID=138286169
* Adds Skylark support to XcTestAppProviderGravatar Sergio Campama2016-11-07
| | | | | -- MOS_MIGRATED_REVID=138231767
* Improve cfg-related warning messages by including a link to the relevant ↵Gravatar Florian Weikert2016-11-07
| | | | | | | | | documentation. Fixes #1877. -- MOS_MIGRATED_REVID=138199724
* aar_import exports AndroidManifest.xml by default.Gravatar Adam Michael2016-11-07
| | | | | | | | | This was an oversight on my part in the original implementation. As one example, the Firebase AAR libraries contain AndroidManifest.xml's with ${applicationId} and Google Play Services contain <meta-data> tags. -- MOS_MIGRATED_REVID=138198047
* EvalException can now show a url for additional informationGravatar Laurent Le Brun2016-11-04
| | | | | | | Add doc for the "read only" error message. -- MOS_MIGRATED_REVID=138194709
* Do not propagate aspect to own attributes when using '*'.Gravatar Googler2016-11-04
| | | | | | | RELNOTES: Do not propagate aspect to its own attributes when using '*'. -- MOS_MIGRATED_REVID=138194456
* Windows: can now remove bazel-* symlinksGravatar Laszlo Csomor2016-11-04
| | | | | | | | | | | | | | | | | This change updates WindowsFileSystem so it: - retrieves the DosFileAttributes instead of the BasicFileAttributes, because the latter does not report junctions as directories - uses just isJunction to decide if a file is a symlink, doesn't look at whether it's a directory (again because java.nio.File also incorrectly reports junctions as non-directories) Fixes https://github.com/bazelbuild/bazel/issues/1850 -- MOS_MIGRATED_REVID=138187220
* Refactor new compilation, archiving, and fully linking logic into a subclass ofGravatar Cal Peyser2016-11-04
| | | | | | | CompilationSupport. -- MOS_MIGRATED_REVID=138185198
* Handle python rules in intellij aspectGravatar Googler2016-11-04
| | | | | -- MOS_MIGRATED_REVID=138182982
* Use main_class as specified in java_test even if use_testrunner is true.Gravatar Dmitry Lomov2016-11-04
| | | | | -- MOS_MIGRATED_REVID=138180229
* Use proto_lang_toolchain() in java_proto_library.Gravatar Carmi Grushko2016-11-04
| | | | | -- MOS_MIGRATED_REVID=138161512
* Use separate "proto" javacopts for all proto compilations.Gravatar Googler2016-11-04
| | | | | -- MOS_MIGRATED_REVID=138143803
* Expose Artifact#isTreeArtifact to Skylark.Gravatar Rumou Duan2016-11-04
| | | | | -- MOS_MIGRATED_REVID=138112581
* Change Bazel default android_manifest_merger to android.Gravatar Adam Michael2016-11-04
| | | | | | | | | | | | | The Firebase Android libraries contain lots of AARs with manifests that include ${applicationId}. As far as I can tell, tools/android/merge_manifests.py only allows for substitution of ${packageName} and not arbitrary placeholder substitution. The new aar_import rule exposes the AARs in <sdk>/extras which include include the Firebase Android libraries. RELNOTES: Default android_manifest_merger is now "android" which uses the official Android manifest merger. http://tools.android.com/tech-docs/new-build-system/user-guide/manifest-merger -- MOS_MIGRATED_REVID=138109902
* Use android javacopts for java_proto_library-related compilations.Gravatar Googler2016-11-04
| | | | | -- MOS_MIGRATED_REVID=138104417
* Make ProtoSourceFileBlacklist take an explicit list of .proto files to ↵Gravatar Carmi Grushko2016-11-03
| | | | | | | | | | | | blacklist. This is intead of taking an attribute name and reading it inside of the class. Motivation: using proto_lang_toolchain() rules means there's no longer an attribute that points at the blacklist. Instead, we have an attribute that points at the toolchain, which itself points at the blacklist. -- MOS_MIGRATED_REVID=138096096
* ProtoCompileActionBuilder takes a list of ToolchainInvocations instead of a ↵Gravatar Carmi Grushko2016-11-03
| | | | | | | map, to emphasize that order matters. -- MOS_MIGRATED_REVID=138090273
* Writes a machine readable representation of BuildEvents to a file (varint ↵Gravatar Eduardo Colaco2016-11-03
| | | | | | | | | | | | | | | | | | | delimited). Adds --experimental_build_event_binary_file option that enables varint delimited proto loggging to the specified file path Adds varint delimited BuildEventStreamTransport and BuildEventStreamerModule Adds BuildEventStreamerModule for configuring and setting up BuildEventStreamer and its associated BuildEventTransports. Adds BuildEventTransportFactory which creates a Set of transports from command options. Moves BuildEventStreamer configuration from BlazeCommandDispatcher and BuildEventStreamerModule -- Change-Id: If71f2b58654879c2509206da47e6d1a846bf397f Reviewed-on: https://bazel-review.googlesource.com/#/c/7010/ MOS_MIGRATED_REVID=138073726
* Implemented repository caching for native maven_jar rules.Gravatar Jingwen Chen2016-11-03
| | | | | | | GITHUB: #1752 -- MOS_MIGRATED_REVID=138072464
* Stop consulting the environment for "originating user" information.Gravatar Googler2016-11-03
| | | | | -- MOS_MIGRATED_REVID=138039276
* Use proto_lang_toolchain in java_lite_proto_library.Gravatar Carmi Grushko2016-11-03
| | | | | -- MOS_MIGRATED_REVID=138005602
* Copy android_manifest_merger from target configuration into host configuration.Gravatar Adam Michael2016-11-03
| | | | | -- MOS_MIGRATED_REVID=138004628
* Do not tickle TimestampGranularityMonitor for stable-status.txt no-op updates.Gravatar Julio Merino2016-11-03
| | | | | | | | | | | | | | | | | When rewriting stable-status.txt, which happens on each build, avoid updating the file's ctime and mtime if the new contents match what is already in the file. This prevents tickling the TimestampGranularityMonitor for what should be a no-op update, which in turn could cause null/incremental builds to stall for up to a second. The problem was magnified on macOS where the default HFS+ file system only has second-level granularity. (This also affects Linux, but because current Linux file systems have milli/nanosecond-level granularity, the wait imposed by TimestampGranularityMonitor is minimal and thus not generally noticeable.) -- MOS_MIGRATED_REVID=137983794
* Refactor MavenDownloader to be a subclass of HttpDownloader to streamline ↵Gravatar Jingwen Chen2016-11-03
| | | | | | | | | | | instantiation of HttpDownloader and RepositoryCache in BazelRepositoryModule. There are sufficient similarities between the download flows of HttpDownloader and MavenDownloader such that we can extend HttpDownloader to MavenDownloader, and reuse method headers such as checkCache and download. GITHUB: #1752 -- MOS_MIGRATED_REVID=137982375
* Adds flag to enable/disable apple_binary from generating and linking ObjC ↵Gravatar Sergio Campama2016-11-03
| | | | | | | protos natively. -- MOS_MIGRATED_REVID=137980688
* java_binary: fix runfiles dir creation on WindowsGravatar Laszlo Csomor2016-11-03
| | | | | | | | | | | | | | | | | Create the runfiles directory for the shell stub script (bazel-bin/foo/bar_bin and bazel-bin/foo/bar_bin.runfiles) but use the batch script as the runfiles provider's executable (bazel-bin/foo/bar_bin.cmd). This way we the shell stub script can still find its runfiles (under its parent directory + its base name + ".runfiles) while "bazel run" can also work on Windows. Fixes https://github.com/bazelbuild/bazel/issues/2025 See https://github.com/bazelbuild/bazel/issues/1925 -- MOS_MIGRATED_REVID=137965442
* Store and use commandId and cookie as ByteStringsGravatar Michajlo Matijkiw2016-11-03
| | | | | | | | | | | | | We wind up doing String -> UTF8 bytes conversion for every message serialized (this happens in protocol buffer land). Do the conversion once and reuse the immutable value instead of doing it for every chunk of output written. Keep this optimization local to RpcOutputStream where we see a lot of repitition - using ByteStrings in place of Strings can get confusing when it comes to logging, so only apply this optimization where it could count. -- MOS_MIGRATED_REVID=137964305
* Also provide test summaries in the build-event streamGravatar Klaus Aehlig2016-11-02
| | | | | | | | | | | For each test target, also have a test summary as children to this event. As test summaries are posted on the event bus anyway, it is enough to make then an instance of BuildEvent. -- Change-Id: Id53e5f1760548a1fa621b1667fdb4470f51a52e8 Reviewed-on: https://bazel-review.googlesource.com/#/c/6931 MOS_MIGRATED_REVID=137961100
* Rollback of commit 0c6e4cdab3c38f8751fb3b944ccaa53866e4c032.Gravatar Adam Michael2016-11-02
| | | | | | | | *** Reason for rollback *** Broke internal builds. -- MOS_MIGRATED_REVID=137959459
* Merge BlazeModule.getEnvironmentExtensions into serverInit / ServerBuilder.Gravatar Ulf Adams2016-11-02
| | | | | -- MOS_MIGRATED_REVID=137955061
* Improve overhead/safety of RecorderStreamGravatar Michajlo Matijkiw2016-11-02
| | | | | | | | | | Bypass converting bytes to string - RecordOutputStream is typically used to wrap stdout/err, which we write bytes to, the string step is waste. Make defensive copies of byte[]s passed to Event since Event doesn't. -- MOS_MIGRATED_REVID=137949714
* Multiplying strings with negative numbers no longer leads to an exception.Gravatar Florian Weikert2016-11-02
| | | | | | | This CL also contains a small refactoring that should make the introduction of list-int-mulitplication easier. -- MOS_MIGRATED_REVID=137938998
* Move createActionCache to ExecutorBuilder.Gravatar Ulf Adams2016-11-02
| | | | | -- MOS_MIGRATED_REVID=137936478
* Description redacted.Gravatar Yue Gan2016-11-02
| | | | | -- MOS_MIGRATED_REVID=137935119
* Add support for --keep-main-dex flag to RexGravatar Googler2016-11-02
| | | | | -- MOS_MIGRATED_REVID=137886595
* Add support for Rex package mapGravatar Googler2016-11-02
| | | | | -- MOS_MIGRATED_REVID=137877037
* Change Bazel default android_manifest_merger to android.Gravatar Adam Michael2016-11-02
| | | | | | | | | | | | | The Firebase Android libraries contain lots of AARs with manifests that include ${applicationId}. As far as I can tell, tools/android/merge_manifests.py only allows for substitution of ${packageName} and not arbitrary placeholder substitution. The new aar_import rule exposes the AARs in <sdk>/extras which include include the Firebase Android libraries. RELNOTES: Default android_manifest_merger is now "android" which uses the official Android manifest merger. http://tools.android.com/tech-docs/new-build-system/user-guide/manifest-merger -- MOS_MIGRATED_REVID=137875695
* Have query Lexer operated directly on StringGravatar Michajlo Matijkiw2016-11-02
| | | | | | | | No need for the char[] in the middle, prevents us from accidentally modifying input, or sucking up ram on huge queries. -- MOS_MIGRATED_REVID=137872573
* Use common logic to create proto action in j2objc proto aspect.Gravatar Rumou Duan2016-11-02
| | | | | -- MOS_MIGRATED_REVID=137871914
* Android native libraries compile with -mstackrealign for 32bit x86 clang.Gravatar Adam Michael2016-11-02
| | | | | | | | | | This is a workaround for a clang bug. See https://code.google.com/p/android/issues/detail?id=220159. RELNOTES: Fix for Android clang++ std::stack segfault on 32bit x86. See https://code.google.com/p/android/issues/detail?id=220159 -- MOS_MIGRATED_REVID=137871199
* Add logging to TimestampGranularityMonitor.Gravatar Julio Merino2016-11-02
| | | | | | | | These new log statements help in understanding what files trigger the TimestampGranularityMonitor's wait logic and when the wait is performed. -- MOS_MIGRATED_REVID=137868235
* Do not tickle TimestampGranularityMonitor for CONSTANT_METADATA artifacts.Gravatar Julio Merino2016-11-02
| | | | | | | | | | | | | | | | | | | | "Constant metadata" artifacts represent real files whose changes should be ignored by the build system. However, these artifacts were triggering the timestamp granularity checks in TimestampGranularityMonitor because the fact that they were "constant metadata" was not respected. Avoid this so that their regeneration does not cause the build to unnecessarily stall. One of these artifacts is the volatile workspace status file, which is unconditionally updated on each build. Before this fix, "blaze build" would get stuck for up to a second waiting for file system timestamps to catch up. With this fix, the artifact is ignored and the wait is gone. This problem is magnified on macOS where the default HFS+ file system only has second-level granularity. (This also affects Linux, but because current Linux file systems have milli/nanosecond-level granularity, the wait imposed by TimestampGranularityMonitor is minimal and thus not generally noticeable.) -- MOS_MIGRATED_REVID=137867586
* ProtoCompileActionBuilder takes ImmutableMap for toolchains, which has a ↵Gravatar Carmi Grushko2016-11-02
| | | | | | | predictable iteration order. -- MOS_MIGRATED_REVID=137864799
generated by cgit v1.2.3 (git 2.39.1) at 2024-09-13 21:21:11 +0000