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
Bazel currently doesn't allow to pass in host java runtime location to
the sh_test scripts. This is tracked in this issue: [1]. Disable the
prolog tests for now, when invoked with newer Java version and consider
to enable the tests again, when the problem is fixed and new Bazel
version with the fix is released.
This is needed to unblock building and passing test with newer Java
versions.
[1] https://github.com/bazelbuild/bazel/issues/9391
Change-Id: Ib08bb7863af4ab6513e07fa61136b1a2b4b4d917
These small examples are designed to run quickly
with the Gerrit prolog-shell, but not depending
on a local Gerrit repository server.
Change-Id: I8f58a6740c6f2c79ae1314f2ae593409ee60440d
Move c.g.g.rules and c.g.g.audit packages to c.g.g.server package to
reflect the real dependencies on server package for these clases.
This allows us to move server code related BUILD rules from general
package c.g.g to c.g.g.server package. With this small refactoring we
can achieve our goal having the BUILD files as close to the sources as
possible. Moreover, this non-intrusive change (no core plugins were
affected) significantly simplifies the whole build structure as this
allows us to eliminate BUILD rule in general c.g.g package.
Before this change a developer must study build files to actually
understand what parts of codes are controlled by c.g.g/BUILD build file.
With this change, it is obvious, because all BUILD files are located as
close as possible to the sources they control.
This changes also leaves place for improvement. At the moment, the
sources can be isolated from the giant java/com/google/gerrit/server
rules, the packages can be moved outside of c.g.g.server package and
de-coupled from java/com/google/gerrit/server rules, as it was already
done with receive, index, metrics and lifecycle packages. These future
and further decomposition of java/com/google/gerrit/server rule is
beyond of the scope of this change.
Change-Id: Iac35422bd9d6ad933c2dded2293c679cdd2aead5
