| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
Fixes #4513
PiperOrigin-RevId: 183060664
|
|
|
|
|
|
|
| |
access.
Change-Id: I6041c51823fa52d6ae55dfe06afd1754ce05ab98
PiperOrigin-RevId: 182904580
|
|
|
|
|
| |
Change-Id: I61def9d449a8b05dde4f96983b84488a71be63a4
PiperOrigin-RevId: 181742031
|
|
|
|
|
|
|
| |
rt.jar etc. no longer exist, retrieve the default bootclasspath contents
using a Java program instead.
PiperOrigin-RevId: 179747945
|
|
|
|
|
|
|
| |
And inject the correct toolchain for the current host_javabase into
tools.WORKSPACE.
PiperOrigin-RevId: 179618337
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 179596587
|
|
|
|
|
|
|
| |
This is now possible because the Bazel release now supports TemplateVariableInfo.
RELNOTES: None.
PiperOrigin-RevId: 178360631
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 177944402
|
|
|
|
|
|
|
| |
This will enable an easier transition from checked-in BUILD files to ones generated by copybara.
RELNOTES: None
PiperOrigin-RevId: 177514519
|
|
|
|
| |
PiperOrigin-RevId: 176521744
|
|
|
|
|
|
| |
When --define EXECUTOR=remote is specified in bazel command, embedded tool singlejar and ijar will be compiled remotely from source.
PiperOrigin-RevId: 174195094
|
|
|
|
| |
PiperOrigin-RevId: 173178028
|
|
|
|
|
|
|
|
|
|
|
| |
See:
* https://docs.oracle.com/javase/9/tools/javac.htm#GUID-AEEC9F07-CB49-4E96-8BC7-BCC2C7F725C9__GUID-38E8A593-FF4E-4EEA-ADC1-84429B08CCA2
* https://docs.oracle.com/javase/9/tools/javac.htm#GUID-AEEC9F07-CB49-4E96-8BC7-BCC2C7F725C9__GUID-A649BE59-30C2-48E8-A766-FA5CD21AB3AF
Fixes #2859
RELNOTES: Enable debug info for Java builds
PiperOrigin-RevId: 166129309
|
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/2829
Without this change, there is no way to use Bazel to build a release Android build (--noincremental_dexing) with java 8 and protos.
RELNOTES: Java protos are compiled to Java 7 bytecode.
PiperOrigin-RevId: 165500316
|
|
|
|
|
|
|
|
|
|
| |
their own.
The alias_rules.bzl hack is required because Bazel at HEAD needs to be able to be built
with released Bazel, which doesn't know these rules yet.
RELNOTES: None.
PiperOrigin-RevId: 161808672
|
|
|
|
|
|
|
|
| |
And instead rely on the flags being set in java_toolchain.jvm_opts.
This change is being made in preparation for JDK 9, which replaces
-Xbootclasspath/p with --patch-module.
PiperOrigin-RevId: 161620182
|
|
|
|
|
|
|
|
|
|
| |
Some projects, eg. TF depends on @bazel_tools//tools/jdk:jni_md_header-<platform>
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/java/src/main/native/BUILD#L70
We already have this for darwin, linux and freebsd, should also provide it for Windows.
RELNOTES: None.
PiperOrigin-RevId: 160248449
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Use Java implementation of singlejar on FreeBSD, and roll forward change 157473007.
*** Original change description ***
Automated g4 rollback of commit d894345ed88f8adce600b66a310b5210d0bcb59c.
*** Reason for rollback ***
Breaks Bazel on FreeBSD: http://ci.bazel.io/view/Dashboard/job/Bazel/JAVA_VERSION=1.8,PLATFORM_NAME=freebsd-11/1542/console
*** Original change description ***
Use cc implementation of singlejar except on Windows.
Change-Id: Ie4a2db2a6fa1ea86f4bdd42cd806f6804a0c56d4
PiperOrigin-RevId: 157729503
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks Bazel on FreeBSD: http://ci.bazel.io/view/Dashboard/job/Bazel/JAVA_VERSION=1.8,PLATFORM_NAME=freebsd-11/1542/console
*** Original change description ***
Use cc implementation of singlejar except on Windows.
Change-Id: Ie4a2db2a6fa1ea86f4bdd42cd806f6804a0c56d4
PiperOrigin-RevId: 157567871
|
|
|
|
|
| |
Change-Id: Ie4a2db2a6fa1ea86f4bdd42cd806f6804a0c56d4
PiperOrigin-RevId: 157473007
|
|
|
|
|
| |
Change-Id: Iad1e07ad55d5304d7c3dbb8bdab856728a91432d
PiperOrigin-RevId: 155375893
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 155003333
|
|
|
|
| |
PiperOrigin-RevId: 154078281
|
|
|
|
|
|
|
|
|
| |
Make Java tool jars available from @bazel_tools.
Now users can point to default Java tool jars in customized
java_toolchain rule defined in project's BUILD file.
PiperOrigin-RevId: 152012191
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks Java 7 tests:
ERROR: missing input file '@bazel_tools//tools/jdk:JavaBuilder_deploy.jar'
http://ci.bazel.io/job/bazel-tests/BAZEL_VERSION=HEAD-jdk7,PLATFORM_NAME=linux-x86_64/670/console
*** Original change description ***
Make Java tool jars available from @bazel_tools.
Now users can point to default Java tool jars in custmized
java_toolchain rule defined in project's BUILD file.
PiperOrigin-RevId: 151699090
|
|
|
|
|
|
|
|
|
|
|
| |
Now users can point to default Java tool jars in custmized
java_toolchain rule defined in project's BUILD file.
--
Change-Id: I064c9646e8681a3f5669d7163b1b3cb5cc0b16b7
Reviewed-on: https://cr.bazel.build/9250
PiperOrigin-RevId: 151422924
MOS_MIGRATED_REVID=151422924
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
rules_closure needs to set go/be#java_plugin.generates_api to 1 for dagger
*** Original change description ***
Disable Java header compilation by default in Bazel.
Enabling this by default broke rules_closure at HEAD:
http://ci.bazel.io/view/Dashboard/job/rules_closure/BAZEL_VERSION=HEAD,PLATFORM_NAME=linux-x86_64/711/console
--
PiperOrigin-RevId: 148132758
MOS_MIGRATED_REVID=148132758
|
|
|
|
|
|
|
|
|
| |
Enabling this by default broke rules_closure at HEAD:
http://ci.bazel.io/view/Dashboard/job/rules_closure/BAZEL_VERSION=HEAD,PLATFORM_NAME=linux-x86_64/711/console
--
PiperOrigin-RevId: 148092235
MOS_MIGRATED_REVID=148092235
|
|
|
|
|
|
|
|
|
|
|
| |
Some projects fail [1] to build after the change that renamed extdir to extclasspath [2].
[1] http://ci.bazel.io/job/rules_appengine/BAZEL_VERSION=HEAD,PLATFORM_NAME=linux-x86_64/564/console
[2] 8153cb80f4a4424640e694cb6ed4792dcc193171
--
PiperOrigin-RevId: 148085503
MOS_MIGRATED_REVID=148085503
|
|
|
|
|
|
|
|
|
| |
The targets contain the entries in the extdir and are used to
construct a classpath, so the label is not actually a directory.
--
PiperOrigin-RevId: 147798672
MOS_MIGRATED_REVID=147798672
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 147449557
MOS_MIGRATED_REVID=147449557
|
|
|
|
|
|
|
|
|
|
| |
This caused a failure in http://ci.bazel.io/job/Gerrit-bazel-tests/368/BAZEL_VERSION=latest,PLATFORM_NAME=ubuntu_15.10-x86_64/console
where the genrule used java from a jdk7 instead of a jdk8.
--
PiperOrigin-RevId: 147198518
MOS_MIGRATED_REVID=147198518
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Header compilation is now explicitly disabled for JDK 7 Bazel using java_toolchain.forcibly_disable_header_compilation
*** Original change description ***
Automated [] rollback of commit 156adeec613ab140a91d73e1147bc688689bcfb7.
*** Reason for rollback ***
Breaks Bazel on JDK 7: http://ci.bazel.io/view/Dashboard/job/bazel-tests/BAZEL_VERSION=HEAD-jdk7,PLATFORM_NAME=linux-x86_64/475/console
*** Original change description ***
Automated [] rollback of commit 5163ec2c0db8fbdc7f367bb4aca5b6d7ae6d80b0.
*** Reason for rollback ***
See unknown commit
*** Original change description ***
Automated [] rollback of commit c9dbd4c1a4a4b4345c0b3924f86e01612ae12807.
*** Reason for rollback ***
Breaks bazel-docker-tests
http://ci.baz...
***
--
PiperOrigin-RevId: 146685610
MOS_MIGRATED_REVID=146685610
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks Bazel on JDK 7: http://ci.bazel.io/view/Dashboard/job/bazel-tests/BAZEL_VERSION=HEAD-jdk7,PLATFORM_NAME=linux-x86_64/475/console
*** Original change description ***
Automated [] rollback of commit 5163ec2c0db8fbdc7f367bb4aca5b6d7ae6d80b0.
*** Reason for rollback ***
See unknown commit
*** Original change description ***
Automated [] rollback of commit c9dbd4c1a4a4b4345c0b3924f86e01612ae12807.
*** Reason for rollback ***
Breaks bazel-docker-tests
http://ci.bazel.io/view/Dashboard/job/bazel-docker-tests/lastCompletedBuild/BAZEL_VERSION=HEAD,PLATFORM_NAME=docker/console
*** Original change description ***
Enable header compilation by default
--
PiperOrigin-RevId: 144443446
MOS_MIGRATED_REVID=144443446
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
See unknown commit
*** Original change description ***
Automated [] rollback of commit c9dbd4c1a4a4b4345c0b3924f86e01612ae12807.
*** Reason for rollback ***
Breaks bazel-docker-tests
http://ci.bazel.io/view/Dashboard/job/bazel-docker-tests/lastCompletedBuild/BAZEL_VERSION=HEAD,PLATFORM_NAME=docker/console
*** Original change description ***
Enable header compilation by default
--
PiperOrigin-RevId: 144344329
MOS_MIGRATED_REVID=144344329
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks bazel-docker-tests
http://ci.bazel.io/view/Dashboard/job/bazel-docker-tests/lastCompletedBuild/BAZEL_VERSION=HEAD,PLATFORM_NAME=docker/console
*** Original change description ***
Enable header compilation by default
--
PiperOrigin-RevId: 144176396
MOS_MIGRATED_REVID=144176396
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 143972504
MOS_MIGRATED_REVID=143972504
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This cycle was due to JacocoCoverage_deploy.jar being an implicit dependency
of java_binary. We do not need the binary during bootstrap because we are not
running with coverage but we need the target. Simply move it to exists as a
java_import in tools/jdk.
Fixes #2269.
To be cherry-picked for #2246.
--
Change-Id: I63aee0e76b305833ac0c0c2cae5abe1cbad5e6d1
Reviewed-on: https://cr.bazel.build/8036
PiperOrigin-RevId: 142537244
MOS_MIGRATED_REVID=142537244
|
|
|
|
|
|
|
|
|
|
| |
PathFragment.getParentDirectory() may return null. Fixes #2212.
Also adds coverage-specific attributes to the java_binary rule.
--
PiperOrigin-RevId: 142516883
MOS_MIGRATED_REVID=142516883
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a semantic change for Bazel, which now observes the --cpu flag when
looking up a Jvm. Use "-default" as a fallback to keep the change backwards
compatible.
RELNOTES[INC]: Bazel now uses the --cpu flag to look up Jvms; it falls back
to "default" if it can't find a Jvm matching the CPU value.
--
MOS_MIGRATED_REVID=135333759
|
|
|
|
|
|
|
| |
directive value.
--
MOS_MIGRATED_REVID=135162267
|
|
|
|
|
|
|
| |
RELNOTES: Persistent workers are now used by default for Java compilation in Bazel, which should speed up your Java builds by ~4x. You can switch back to the old behavior via --strategy=Javac=standalone. Check out http://www.bazel.io/blog/2015/12/10/java-workers.html for more details.
--
MOS_MIGRATED_REVID=128801059
|
|
|
|
|
|
|
|
|
| |
-XX:TieredStopAtLevel=1 instead of -client, as the latter is ignored on 64-bit JVMs since at least JDK 6.
The new flags have been shown to cut down CPU time by 50% due to reduced time spent in JIT and improving overall run time for short running actions, some times also cutting them in half.
--
MOS_MIGRATED_REVID=127536578
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125589653
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-XX:TieredStopAtLevel=1 instead of -client, as the latter is ignored on 64-bit JVMs since at least JDK 6.
The new flags have been shown to cut down CPU time by 50% due to reduced time spent in JIT and improving overall run time for short running actions, some times also cutting them in half.
Here's a benchmark of Bazel building itself, giving a nice 2-4x speedup:
./output/bazel clean && ./output/bazel build //src:bazel
Bazel before this change:
INFO: Elapsed time: 197.783s, Critical Path: 194.10s
INFO: Elapsed time: 198.928s, Critical Path: 195.65s
INFO: Elapsed time: 194.913s, Critical Path: 191.56s
Bazel before this change with --strategy=Javac=worker:
INFO: Elapsed time: 130.436s, Critical Path: 124.27s
INFO: Elapsed time: 116.114s, Critical Path: 112.30s
INFO: Elapsed time: 116.852s, Critical Path: 84.45s
Bazel with this change:
INFO: Elapsed time: 121.625s, Critical Path: 119.08s
INFO: Elapsed time: 119.401s, Critical Path: 115.80s
INFO: Elapsed time: 121.198s, Critical Path: 119.03s
Bazel with this change and --strategy=Javac=worker:
INFO: Elapsed time: 54.456s, Critical Path: 51.28s
INFO: Elapsed time: 53.272s, Critical Path: 51.09s
INFO: Elapsed time: 52.966s, Critical Path: 49.86s
Bazel with this change and --strategy=Javac=worker and stripping -XX:TieredStopAtLevel=1 from JVM flags when using workers:
INFO: Elapsed time: 61.599s, Critical Path: 58.93s
INFO: Elapsed time: 48.695s, Critical Path: 45.02s
INFO: Elapsed time: 46.874s, Critical Path: 43.91s
INFO: Elapsed time: 46.174s, Critical Path: 43.32s
(The latter is a possible optimization for workers and it's also nice to know that the limited tiered compilation does not hurt their performance.)
--
MOS_MIGRATED_REVID=125448089
|
|
|
|
|
|
|
|
| |
This allows --experimental_java_header_compilation=true to be used with Bazel.
It is still off by default.
--
MOS_MIGRATED_REVID=121623213
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Along the path, fix the build for JDK 7 and get rid of
most ugliness in the JDK 7 build. Now simply setting
JAVA_VERSION to 1.7 will build a JDK 7 compatible version.
Fixes #1159.
--
Change-Id: I9599283844a57d9e053f12d37445907f22a9232e
Reviewed-on: https://bazel-review.googlesource.com/#/c/3452
MOS_MIGRATED_REVID=120332747
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change disables --java_langtools, --javabuilder_top, --singlejar_top,
--genclass_top, and --ijar_top, and finishes replacing them with
java_toolchain.{javac,javabuilder,singlejar,genclass,ijar}.
RELNOTES: Replace --java_langtools, --javabuilder_top, --singlejar_top,
--genclass_top, and --ijar_top with
java_toolchain.{javac,javabuilder,singlejar,genclass,ijar}
--
MOS_MIGRATED_REVID=120154954
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks ci.bazel.io
While the basics for fixing the build is easy (just a few typos in packages building), fixing the test is a bit more tricky. I see only one solution for fixing the test: use a select statement that would select the good bazel version but that would always pull JavaBuilder as an external dependency when we do test.
Better roll this back then check the JavaBuilder 0.1.0 as a binary in third_party before rolling forward (a similar change is still needed to decouple running the test and building the binary for JDK 7)
*** Original change description ***
Refactor build for JDK 7
Now the JDK 7 tuning happens all in Bazel, removing logic
from the CI script. It uses remote repositories to access
JDK 7 dependencies.
--
MOS_MIGRATED_REVID=119773123
|
|
|
|
|
|
|
|
|
|
|
| |
Now the JDK 7 tuning happens all in Bazel, removing logic
from the CI script. It uses remote repositories to access
JDK 7 dependencies.
--
Change-Id: Iff590c6642ca5b2343aa15096f8fd837d1c80787
Reviewed-on: https://bazel-review.googlesource.com/#/c/3327
MOS_MIGRATED_REVID=119634530
|