tools/eclipse: find jar from rules_jvm_external

The Eclipse script crawls through Bazel `output_base` to find
the project jar dependencies. It recognizes location written by

When using `rules_jvm_external` artifacts are symlinked under different
paths and the utility is unable to find them. It results in a generated
`.classpath` missing most entries.

`rules_jvm_external` symlinks the cached jar under:

This change adds support to find them there.

In order to have the JavaDoc displayed, the source jar have to be
retrieved as well which `rules_jvm_external` does not do by default. One
has to turn that on explicitly:

  load("@rules_jvm_external//:defs.bzl", "maven_install")
    artifacts = ['x', 'y', 'z' ],
    fetch_sources = True,

The source jar will then be made available with the suffix
`-sources.jar`, unlike `maven_jar` which uses `-src.jar`.

Change-Id: Ifb56b2f84b5f38a700362c1de436cd4b4714dc2f
2 files changed
tree: 1117df8e2c9ecef082f54a68b907a3e7a0516b8b
  1. lib/
  2. tools/
  3. .gitignore
  4. bouncycastle.bzl
  5. BUILD
  7. gerrit_api.bzl
  8. gerrit_api_version.bzl
  9. gerrit_plugin.bzl
  10. gerrit_polymer.bzl
  12. rules_python.bzl

Gerrit Code Review Rules for Bazel


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.

  name = "com_googlesource_gerrit_bazlets",
  remote = "",
  commit = "928c928345646ae958b946e9bbdb462f58dd1384",
load("@com_googlesource_gerrit_bazlets//:gerrit_api.bzl", "gerrit_api")

The version parameter allows to override the default API. For release version numbers, make sure to also provide artifacts' SHA1 sums via the plugin_api_sha1 and acceptance_framework_sha1 parameters:

load("@com_googlesource_gerrit_bazlets//:gerrit_api.bzl", "gerrit_api")
gerrit_api(version = "3.2.1",
           plugin_api_sha1 = "47019cf43ef7e6e8d2d5c0aeba0407d23c93699c",
           acceptance_framework_sha1 = "6252cab6d1f76202e57858fcffb428424e90b128")

If the version ends in -SNAPSHOT, the jars are consumed from the local Maven repository (~/.m2) per default assumed to be and the SHA1 sums can be omitted:

load("@com_googlesource_gerrit_bazlets//:gerrit_api.bzl", "gerrit_api")
gerrit_api(version = "3.3.0-SNAPSHOT")

Basic Example

Suppose you have the following directory structure for a simple plugin:

├── src
│   └── main
│       ├── java
│       └── resources

To build this plugin, your BUILD can look like this:

load("//tools/bzl:plugin.bzl", "gerrit_plugin")

    name = "reviewers",
    srcs = glob(["src/main/java/**/*.java"]),
    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, deps, manifest_entries):

Implicit output target

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