| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
| |
lombok-ast 0.2.3 and dependencies asm-analysis 5.0.4, asm-tree 5.0.4)
Change-Id: I37d82e442d660ebf6182c1196938125aa8be12c4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://github.com/3breadt/dd-plist/commit/3fa1fa56c82df169e06079feb54ba281ad41cae6
which stabilizes the ordering of items in the plist and is equivalent to what happens in Apple's reference code.
https://github.com/3breadt/dd-plist/commit/a5fb37384d4ca7a3b5039a7605ca0e9ca926a6ec
which outputs ids in the plist equivalent to Apple's reference code.
We still differ from Apple's code in that we de-dupe booleans, arrays, and dictionaries which produces smaller binaries. Via testing I have determined that the tooling that was having trouble with our "bad" plists, appears to be happy with our output if we continue our de-duping so I left it in there. Fixing it so that it was exactly equivalent to Apple's output would be a significantly larger engineering effort.
--
PiperOrigin-RevId: 142166474
MOS_MIGRATED_REVID=142166474
|
|
|
|
| |
Change-Id: I4e99ca21c95a1f6a4f46885adbee560f2a08ef17
|
|
|
|
|
|
|
|
| |
0 is not a valid DOS timestamp, days and months start at 1.
--
PiperOrigin-RevId: 141818782
MOS_MIGRATED_REVID=141818782
|
|
|
|
|
|
| |
These are just bloating the git repository size.
Change-Id: I734cf6282eb6853217f68f0b33109b16424bde50
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 645dbc4 moved the file stating logic to
platform_utils.cc into the `stat_file` method,
then commit 8d6da00 added error reporting to that
method so callers wouldn't need to report errors
on their own. Problem is, one of the callers was
using stat_file for simple file existence checking
so reporting an error there was spurious.
Fixes https://github.com/bazelbuild/bazel/issues/2201
--
Change-Id: I40d1ee2bad8f3d03627c0b5c0bfd593bb5289d23
Reviewed-on: https://cr.bazel.build/7810
PiperOrigin-RevId: 141739581
MOS_MIGRATED_REVID=141739581
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 141396618
MOS_MIGRATED_REVID=141396618
|
|
|
|
|
|
|
|
| |
We are no longer using the checked-in apksigner jar, instead we are now reading this JAR from the Android build tools. A follow-up change will remove the actual JAR. One small step towards making the Bazel binary smaller :)
--
PiperOrigin-RevId: 141355143
MOS_MIGRATED_REVID=141355143
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 141322619
MOS_MIGRATED_REVID=141322619
|
|
|
|
|
|
|
|
|
| |
We were using this JAR in the interim until it was released in the
Android SDK build tools. As of build tools version 24.0.3, it is
released and Bazel now uses that JAR.
Change-Id: I927480153aa45b71d7fbde995f9deae99c759f86
RELNOTES: None
|
|
|
|
|
|
| |
https://github.com/google/error-prone-javac/archive/9-dev-r3297-1.zip
Change-Id: I10f28f2376d0073045ed0b3e0d7e4f1b1987472a
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We can now build //third_party/ijar/...:all with
--cpu=x64_windows_msvc.
We also have to use --output_user_root=/c/tmp
or something similarly short because
//third_party/zlib tickles https://github.com/bazelbuild/bazel/issues/2145
This change takes us closer to compiling Bazel
with MSVC.
See https://github.com/bazelbuild/bazel/issues/2107
--
PiperOrigin-RevId: 140846600
MOS_MIGRATED_REVID=140846600
|
|
|
|
|
|
|
|
|
|
| |
Fixes compilation on FreeBSD
--
Change-Id: Iedaa9e08615b8a52fae6f19c867d419938a08411
Reviewed-on: https://cr.bazel.build/7591
PiperOrigin-RevId: 140838599
MOS_MIGRATED_REVID=140838599
|
|
|
|
|
|
|
|
|
|
|
|
| |
zip_main.cc no longer needs <unistd.h>.
This change takes us closer to compiling ijar,
thus Bazel, with MSVC.
See https://github.com/bazelbuild/bazel/issues/2157
See https://github.com/bazelbuild/bazel/issues/2107
--
MOS_MIGRATED_REVID=140724421
|
|
|
|
|
|
|
|
|
|
|
|
| |
zip_main.cc no longer needs <unistd.h>.
This change takes us closer to compiling ijar,
thus Bazel, with MSVC.
See https://github.com/bazelbuild/bazel/issues/2157
See https://github.com/bazelbuild/bazel/issues/2107
--
MOS_MIGRATED_REVID=140723658
|
|
|
|
|
|
|
|
|
|
|
| |
This change takes us closer to compiling ijar,
thus Bazel, with MSVC.
See https://github.com/bazelbuild/bazel/issues/2157
See https://github.com/bazelbuild/bazel/issues/2107
--
MOS_MIGRATED_REVID=140722341
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=140719621
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change takes us closer to compiling ijar,
thus Bazel, with MSVC.
Also update the StatFile method added by
unknown commit to report any errors.
See https://github.com/bazelbuild/bazel/issues/2157
See https://github.com/bazelbuild/bazel/issues/2107
--
MOS_MIGRATED_REVID=140719249
|
|
|
|
|
|
|
|
|
|
| |
This change takes us closer to compiling ijar,
thus Bazel, with MSVC.
See https://github.com/bazelbuild/bazel/issues/2107 and https://github.com/bazelbuild/bazel/issues/2157
--
MOS_MIGRATED_REVID=140717828
|
| |
|
|
|
|
|
|
|
|
|
| |
java_xxx_proto_library rules now look for toolchains in the external repo @com_google_protobuf_xxx//:xxx_toolchain
This still requires getting protobuf's GitHub repository to build with Bazel.
--
MOS_MIGRATED_REVID=140420903
|
|
|
|
| |
Change-Id: I5da74a545eb4e0a0455ee1014c5a253ae02cd6c7
|
|
|
|
|
|
|
|
|
|
| |
...instead of using checked-in binaries. Also update the
update instructions accordingly.
--
Change-Id: I5a52abbdc1c34883d179b4559064c464b958714f
Reviewed-on: https://cr.bazel.build/6831
MOS_MIGRATED_REVID=140348730
|
|
|
|
|
|
|
|
| |
This is a copy of the relevant sources from
https://github.com/grpc/grpc-java/ version 0.15.0
to build the grpc-java plugin.
Change-Id: Ideaf6406d8c54eaf98d0cedf74af604061622c3e
|
|
|
|
|
|
| |
...as we build protoc from source now.
Change-Id: Ib9662345cf98af9b90da7422658796ee4937e1ce
|
|
|
|
|
|
|
|
|
|
| |
Use the provided sources to build the protoc binary instead of
using the committed binaries.
--
Change-Id: I3df01e9f400e3cebbd1fe3ce74c6142c93c58b6c
Reviewed-on: https://cr.bazel.build/6732
MOS_MIGRATED_REVID=140192644
|
|
|
|
|
|
|
|
|
|
|
| |
The behavior of ftruncate on WSL is not same as standard Linux due to a bug, it'll fail on maped file.
This commit fix the bug by munmap the file before ftruncate.
Closes #2108.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2108
MOS_MIGRATED_REVID=140134115
|
|
|
|
|
|
|
| |
Fixes #2119 and related bootstrap breakage.
Change-Id: I7ca5b9f509e182780f3486c22bf30da3d4104f15
RELNOTES: None.
|
|
|
|
|
|
|
| |
preparation of removing the older one from //third_party/protobuf.
--
MOS_MIGRATED_REVID=140023015
|
|
|
|
|
|
| |
https://bazel-review.googlesource.com/#/c/7270/.
Change-Id: Ie2cc95521bb1c6287dcdfb083e35bf4c15c7abd3
|
|
|
|
|
|
|
| |
build. See https://bazel-review.googlesource.com/#/c/7270/ for details.
--
MOS_MIGRATED_REVID=139580987
|
|
|
|
|
|
|
| |
This should allow to use pkg_tar from project that use python 3 (e.g. TensorFlow).
--
MOS_MIGRATED_REVID=139561406
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Causes NPEs in tests that use AutoValue, on Kokoro and CI.
Bazel uses TestRunner_deploy.jar to run tests. To save time, we use the latest Bazel release to run tests. Therefore, we use a TestRunner_deploy.jar with an AutoValue 1.2 embedded.
If the test requires AV itself, we use the one from HEAD, which is 1.4-rc1, therefore causing one-definition rule violations.
Once we release a TestRunner without AV (commit 90b5b19927540fc1e1c9e1a7fbd05c816ae0e4e2), we can roll forward.
error: @AutoValue processor threw an exception: java.lang.NullPointerException
abstract static class AutoValuedClass implements TransitiveInfoProvider {
^
at com.google.auto.value.processor.AutoValueProcessor.getFieldOfClasses(AutoValueProcessor.java:566)
at com.google.auto.value.processor.AutoValueProcessor.allMethodExcludedAnnotations(AutoValueProcessor.java:818)
at com.google.auto.value.processor.AutoValueProcessor.defineVarsForType(AutoValueProcessor.java:763)
at com.google.auto.value.processor.AutoValueProcessor.processType(AutoValueProcessor.java:488)
at com.google.auto.value.processor.AutoValueProcessor.process(AutoValueProcessor.java:195)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:803)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:715)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$2000(JavacProcessingEnvironment.java:93)
at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1023)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1130)
at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1141)
at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:832)
at com.sun.tools.javac.main.Main.compile(Main.java:253)
at com.google.devtools.build.buildjar.javac.BlazeJavacMain.compile(BlazeJavacMain.java:140)
at com.google.devtools.build.buildjar.javac.BlazeJavacMain.compile(BlazeJavacMain.java:132)
at com.google.devtools.build.buildjar.AbstractJavaBuilder$1.invokeJavac(AbstractJavaBuilder.java:66)
at com.google.devtools.build.buildjar.ReducedClasspathJavaLibraryBuilder.compileSources(ReducedClasspathJavaLibraryBuilder.java:81)
at com.google.devtools.build.buildjar.AbstractJavaBuilder.compileJavaLibrary(AbstractJavaBuilder.java:69)
at com.google.devtools.build.buildjar.AbstractJavaBuilder.run(AbstractJavaBuilder.java:108)
at com.google.devtools.build.buildjar.BazelJavaBuilder.processRequest(BazelJavaBuilder.java:92)
at com.google.devtools.build.buildjar.BazelJavaBuilder.runPersistentWorker(BazelJavaBuilder.java:70)
at com.google.devtools.build.buildjar.BazelJavaBuilder.main(BazelJavaBuilder.java:47)
*** Original change description ***
Bazel to use AutoValue 1.4-rc1.
The big improvement is the addition of @AutoValue.CopyAnnotations, which allows AutoValue classes to be exposed to Skylark via @SkylarkModule.
--
MOS_MIGRATED_REVID=139361042
|
|
|
|
|
|
|
| |
The big improvement is the addition of @AutoValue.CopyAnnotations, which allows AutoValue classes to be exposed to Skylark via @SkylarkModule.
--
MOS_MIGRATED_REVID=139336396
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=139238158
|
|
|
|
|
|
|
| |
Actually using it will be done in a separate commit, as is removing the
old versions.
Change-Id: I049d63da3c5c206278c7d708ccb687dc78e6ea34
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke bazel with java 7
see http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel/982/
*** Original change description ***
Have Bazel use the the prebuilt guava jars from the 21.0-20161101 daily build. See https://bazel-review.googlesource.com/#/c/7270/ for details (do not submit until that commit occurs).
--
MOS_MIGRATED_REVID=138618115
|
|
|
|
|
|
|
| |
build. See https://bazel-review.googlesource.com/#/c/7270/ for details (do not submit until that commit occurs).
--
MOS_MIGRATED_REVID=138553338
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(downloaded from
https://oss.sonatype.org/content/repositories/snapshots/com/google/guava/guava-testlib/21.0-SNAPSHOT/),
in order to get
https://github.com/google/guava/commit/ef386251e5cc485fb72890fff67830340635e44b.
nharmata@nharmata1:~/bazel$ grep InternerBuilder
third_party/guava/guava-19.0.jar
nharmata@nharmata1:~/bazel$ grep InternerBuilder
third_party/guava/guava-21.0-20161101.jar
Binary file third_party/guava/guava-21.0-20161101.jar matches
nharmata@nharmata1:~/bazel$
I want to use the new InternerBuilder api in Bazel.
nharmata@nharmata1:~/bazel$ md5sum third_party/guava/*.jar
b31066276b1352cf720254b3d1342b11
third_party/guava/guava-21.0-20161101.jar
16def9388e9482eee2454a7f9d019697
third_party/guava/guava-testlib-21.0-20161101.jar
nharmata@nharmata1:~/bazel$
Change-Id: I7784acaf1c194a78a073eb37d18787326dbb2293
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Use proto_lang_toolchain() in java_proto_library, after fixing breakage.
Verified on Jenkins, http://ci.bazel.io/job/Gerrit-bazel-tests/169/
*** Original change description ***
Automated [] rollback of commit a396b070ae36032a973672e11145533621c39edc.
*** 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=138432193
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138161512
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137500893
|
|
|
|
|
|
|
|
|
| |
We have stopped using iossim in Bazel and replaced it with direct access to xcode's APIs. As a result we can clean up our code base by removing any references to iossim.
RELNOTES:none
--
MOS_MIGRATED_REVID=137165435
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=136574107
|
|
|
|
|
|
|
|
|
|
|
| |
The "protobuf_python" target references a "protobuf_python_srcs" target in its deps, which does not exist, causing a build error when I tried to run "bazel build //src/main/...":
ERROR: /Users/philwo/src/bazel/third_party/protobuf/3.0.0/BUILD:70:1: in deps attribute of py_library rule //third_party/protobuf/3.0.0:protobuf_python: rule '//third_party/protobuf/3.0.0:protobuf_python_srcs' does not exist. Since this rule was created by the macro 'py_proto_library', the error might have been caused by the macro implementation in /Users/philwo/src/bazel/third_party/protobuf/protobuf.bzl:256:12.
I think the "python_srcs" target should actually be called "protobuf_python_srcs". With that change, the build works.
--
MOS_MIGRATED_REVID=136467485
|
|
|
|
|
|
|
|
|
|
|
| |
We have added support for Linux s390x platform in Bazel.
Closes #1891.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1891
MOS_MIGRATED_REVID=135777047
|
|
|
|
|
|
|
|
| |
http://repo1.maven.org/maven2/com/google/errorprone/error_prone_core/2.0.13/error_prone_core-2.0.13.jar
http://repo1.maven.org/maven2/com/google/errorprone/error_prone_annotations/2.0.13/error_prone_annotations-2.0.13.jar
http://repo1.maven.org/maven2/com/google/errorprone/error_prone_annotation/2.0.13/error_prone_annotation-2.0.13.jar
Change-Id: I4e8e8d82161860f9c758c0a957b0ccab7cbcb1bb
|
|
|
|
| |
This is a partial import of the patch 8ba828096961b72c8eb93f327719c5de8349581c by Steven Dee <steve@smartercode.net>. The patch cannot be imported in one piece because we store the third-party libraries in the Bazel repository separately from the actual source code of Bazel.
|
|
|
|
|
|
|
|
|
|
|
| |
Older android_ide_common does not handle BCP 47,
so we update the code to handle that and remove
most of the workarounds. This also pulls in a
fix for 3-letter locales, unblocks resource
shrinking whitelisting, etc.
--
MOS_MIGRATED_REVID=135396457
|