gerrit/lib/jgit/org.eclipse.jgit.junit/BUILD

load("//lib/jgit:jgit.bzl", "jgit_dep")

java_library(
    name = "junit",
    testonly = 1,
    data = ["//lib:LICENSE-DO_NOT_DISTRIBUTE"],
    visibility = ["//visibility:public"],
    exports = [jgit_dep("@jgit_junit//jar")],
    runtime_deps = ["//lib/jgit/org.eclipse.jgit:jgit"],
)
Simplify local JGit development Put all the logic in jgit.bzl, where a single edit suffices to get the local flavor. Given that all sha1 for jgit dependencies are in jgit.bzl, we can remove the constants and use sha1 values directly. Change-Id: Icabf651e02f226e5c025457d54588074a11ae283 2017-03-23 16:24:09 +01:00			`load("//lib/jgit:jgit.bzl", "jgit_dep")`

Implement Bazel build To run the tests: bazel test //... To build the Gerrit plugin API, run: bazel build gerrit-plugin-api:plugin-api_deploy.jar To build the Gerrit extension API, run: bazel build gerrit-extension-api:extension-api_deploy.jar TODOs: Licenses Reduce visibility (all public for now) Generate HTML Documentation Core plugins gerrit_plugin() rule to build plugins in tree and standalone modes GWT UI (only gwt_module() skylark rule is provided, no gwt_binary()) PolyGerrit UI WAR Publish artifacts to Maven Central Ask Bazel team to add Gerrit to their CI on ci.bazel.io Contributed-By: Han-Wen Nienhuys <hanwen@google.com> Change-Id: I9a86e670882a44a5c966579cdeb8ed79b1590de3 2016-05-21 19:55:01 +02:00			`java_library(`
Bazel: Reformat build files Reformat the Bazel build files with the buildifier tool [1]. The style is different for Bazel files. Most notably, indentation level is 4 spaces instead of 2, and " is used instead of '. [1] https://github.com/bazelbuild/buildifier Change-Id: I95c0c6f11b6d76572797853b4ebb5cee5ebd3c98 2016-11-30 08:52:06 +01:00			`name = "junit",`
Bazel: Allow to consume jgit from development tree Now that Bazel build for JGit is fully implemented, we can document the process of routing the JGit dependency to the development tree instead of consuming it from Central or ~/.m2 local repository: 1. Activate local jgit repository in WORKSPACE file: local_repository( name = "jgit", path = "/home/<user>/projects/jgit", ) 2. Uncomment alias to jgit repository in lib/jgit/**/BUILD files. It shouldn't be needed and is tracked under this issue upstream: [1]: alias( name = "jgit-alias", actual = select({ "@//lib:jgit-dev": "@jgit//org.eclipse.jgit:jgit", "//conditions:default": "@jgit_lib//jar", }), visibility = ["//visibility:public"], ) Test plan: Update local JGit tree, run tests and verify that local JGit tree modifications are relfected in gerrit build: $ bazel build --define jgit-dev=1 headless To consume JGit from Central, do not pass jgit-dev=1: $ bazel test ... [1] https://github.com/bazelbuild/bazel/issues/2707 Change-Id: I1b0fee7df802f6cbd54acbb0bc73157e2b8bc7cf 2016-11-06 18:07:10 +01:00			`testonly = 1,`
Bazel: Reformat build files Reformat the Bazel build files with the buildifier tool [1]. The style is different for Bazel files. Most notably, indentation level is 4 spaces instead of 2, and " is used instead of '. [1] https://github.com/bazelbuild/buildifier Change-Id: I95c0c6f11b6d76572797853b4ebb5cee5ebd3c98 2016-11-30 08:52:06 +01:00			`data = ["//lib:LICENSE-DO_NOT_DISTRIBUTE"],`
			`visibility = ["//visibility:public"],`
Simplify local JGit development Put all the logic in jgit.bzl, where a single edit suffices to get the local flavor. Given that all sha1 for jgit dependencies are in jgit.bzl, we can remove the constants and use sha1 values directly. Change-Id: Icabf651e02f226e5c025457d54588074a11ae283 2017-03-23 16:24:09 +01:00			`exports = [jgit_dep("@jgit_junit//jar")],`
Bazel: Reformat build files Reformat the Bazel build files with the buildifier tool [1]. The style is different for Bazel files. Most notably, indentation level is 4 spaces instead of 2, and " is used instead of '. [1] https://github.com/bazelbuild/buildifier Change-Id: I95c0c6f11b6d76572797853b4ebb5cee5ebd3c98 2016-11-30 08:52:06 +01:00			`runtime_deps = ["//lib/jgit/org.eclipse.jgit:jgit"],`
Implement Bazel build To run the tests: bazel test //... To build the Gerrit plugin API, run: bazel build gerrit-plugin-api:plugin-api_deploy.jar To build the Gerrit extension API, run: bazel build gerrit-extension-api:extension-api_deploy.jar TODOs: Licenses Reduce visibility (all public for now) Generate HTML Documentation Core plugins gerrit_plugin() rule to build plugins in tree and standalone modes GWT UI (only gwt_module() skylark rule is provided, no gwt_binary()) PolyGerrit UI WAR Publish artifacts to Maven Central Ask Bazel team to add Gerrit to their CI on ci.bazel.io Contributed-By: Han-Wen Nienhuys <hanwen@google.com> Change-Id: I9a86e670882a44a5c966579cdeb8ed79b1590de3 2016-05-21 19:55:01 +02:00			`)`