Google Git
Sign in
gerrit / bazlets / 28d12c28df242b21855d4bebf8cca12b9ffcb900
commit28d12c28df242b21855d4bebf8cca12b9ffcb900[log] [tgz]
authorDavid Ostrovsky <david@ostrovsky.org>Tue Jan 23 22:55:01 2018 +0100
committerDavid Ostrovsky <david@ostrovsky.org>Tue Jan 23 22:59:43 2018 +0100
tree9a9a318aa1309235093d952cda1928f9177c8014
parent3f2b830464b57db97faaac269dcf869653bd9b80 [diff]
Exclude GWT library from gerrit_plugin_gwtui artifact

GWT user and dev libraries are shaded into gerrit_plugin_gwtui and
interferes the compilation of GWT plugins in standalone build mode.

The right way to fix that would be to avoid the inclusion of the
GWT libraries in gerrit_plugin_gwtui artifact in the first place.
As quick and dirty workaround strip the GWT libraries during fetch
of the plugin API from Central.

Change-Id: I76762cc1adf101f865ee58ff479a078a73211657
1 file changed
tree: 9a9a318aa1309235093d952cda1928f9177c8014
  1. lib/
  2. tools/
  3. .gitignore
  4. bouncycastle.bzl
  5. BUILD
  6. COPYING
  7. gerrit_api.bzl
  8. gerrit_api_maven_local.bzl
  9. gerrit_gwt.bzl
  10. gerrit_plugin.bzl
  11. README.md
  12. WORKSPACE
README.md

Gerrit Code Review Rules for Bazel

Overview

These build rules are used for building Gerrit Code Review plugins with Bazel. Plugins are compiled as .jar files containing plugin code and dependencies.

Setup

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()

Basic Example

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

gerrit_plugin(name, srcs, resources, gwt_module, deps, manifest_entries):

Implicit output target

  • <name>.jar: library containing built plugin jar