cf4f70bc2a
This change also removes the support for building with Java 9
and 10.
Test Plan:
* Run the tests with Java 8 toolchain (the same as before this change):
$ bazel test //...
* Run the tests with remote Java 11 toolchain (new feature added here):
$ bazel test --host_javabase=@bazel_tools//tools/jdk:remote_jdk11 \
--javabase=@bazel_tools//tools/jdk:remote_jdk11 \
--host_java_toolchain=@bazel_tools//tools/jdk:toolchain_java11 \
--java_toolchain=@bazel_tools//tools/jdk:toolchain_java11 \
//...
Change-Id: Ib67dcc50a43f998bc8f5a363a8f681e3693d1f26
16 lines
425 B
Python
16 lines
425 B
Python
package(default_visibility = ["//visibility:public"])
|
|
|
|
DUMMY = ["dummy.sh"]
|
|
|
|
# Enable prologtests on newer Java versions again, when this Bazel bug is fixed:
|
|
# https://github.com/bazelbuild/bazel/issues/9391
|
|
sh_test(
|
|
name = "test_examples",
|
|
srcs = select({
|
|
"//:java11": DUMMY,
|
|
"//:java_next": DUMMY,
|
|
"//conditions:default": ["run.sh"],
|
|
}),
|
|
data = glob(["*.pl"]) + ["//:gerrit.war"],
|
|
)
|