| commit | 4e6783e59b2ff594470c13140ab0e6ed74fafef8 | [log] [tgz] |
|---|---|---|
| author | David Pursehouse <dpursehouse@collab.net> | Fri Sep 06 15:03:13 2019 +0900 |
| committer | David Pursehouse <dpursehouse@collab.net> | Fri Sep 06 15:45:46 2019 +0900 |
| tree | 96fddea4fd2d8a88eafec66c8d5fe7f1934c3ece | |
| parent | 2aabb43cc8f50fc8c1359749f88126f166842f41 [diff] |
Support bazelisk or bazel in tools/eclipse/project.py It is recommended to use bazelisk instead of bazel directly, however it is also perfectly reasonable to use bazel directly. Update the eclipse script to default to looking for bazelisk then bazel, but to continue to allow explicit overrides. This should allow people who do not have bazelisk to not be broken, but people who have installed bazelisk to have it be the program run by default. This also causes whichever of the two was found to to go into .bazel_path which will influence what eclipse uses. Based on the change from Monty Taylor [1] in core Gerrit. [1] https://gerrit-review.googlesource.com/c/gerrit/+/234727 Bug: Issue 11359 Change-Id: I2490e479d16bdad64c771a38e6cce73decb062a6
These build rules are used for building Gerrit Code Review plugins with Bazel. Plugins are compiled as .jar files containing plugin code and dependencies.
To be able to use the Gerrit rules, you must provide bindings for the plugin API jars. The easiest way to do so is to add the following to your WORKSPACE file, which will give you default versions for Gerrit plugin API.
git_repository( name = "com_github_davido_bazlets", remote = "https://github.com/davido/bazlets.git", commit = "2ede19cb2d2dd9d04bcb70ffc896439a27e5d50d", ) load("@com_github_davido_bazlets//:gerrit_api.bzl", "gerrit_api")
Another option is to consume snapshot version of gerrit plugin API from local Maven repository (~/.m2). To use the snapshot version special method is provided:
load("@com_googlesource_gerrit_bazlets//:gerrit_api_maven_local.bzl", "gerrit_api_maven_local") gerrit_api_maven_local()
Suppose you have the following directory structure for a simple plugin:
[workspace]/
WORKSPACE
BUILD
src/main/java/
src/main/resources/
[...]
To build this plugin, your BUILD can look like this:
load("//tools/bzl:plugin.bzl", "gerrit_plugin") gerrit_plugin( name = "reviewers", srcs = glob(["src/main/java/**/*.java"]), gwt_module = "com.googlesource.gerrit.plugins.reviewers.ReviewersForm", manifest_entries = [ "Gerrit-PluginName: reviewers", "Gerrit-Module: com.googlesource.gerrit.plugins.reviewers.Module", ], resources = glob(["src/main/**/*"]), )
Now, you can build the Gerrit plugin by running bazel build <plugin>.
For a real world example, see the reviewers plugin.
gerrit_plugin(name, srcs, resources, gwt_module, deps, manifest_entries):
<name>.jar: library containing built plugin jar