| commit | b07aa8462f2618a83f3b52d6150faa831b24d3e3 | [log] [tgz] |
|---|---|---|
| author | Marco Miller <marco.miller@ericsson.com> | Wed Jan 15 11:59:43 2020 -0500 |
| committer | Marco Miller <marco.miller@ericsson.com> | Wed Jan 15 16:38:39 2020 -0500 |
| tree | e226a35b659778d948862aaf0849eb5625ef1f50 | |
| parent | e48c6a61d5a3f9ab4589f324fc85b8e3777d8854 [diff] |
Use now mandatory https protocol for MAVEN_CENTRAL Do so according to [1], which now points to the explanation [2]. Prevently use https also for the gerrit-maven.storage.googleapis.com domain. [1] http://repo1.maven.org/maven2/ [2] "Effective January 15, 2020, The Central Repository no longer supports insecure communication over plain HTTP and requires that all requests to the repository are encrypted over HTTPS. If you're receiving this error, then you need to replace all URL references to Maven Central with their canonical HTTPS counterparts." Bug: Issue 12170 Change-Id: I001fb42b1a8e97d262cfcffbdb9451094b1b0430
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