Documentation: Refactor to match other plugin documentation Move in-tree testing section before eclipse-related section for consistency across other plugins and also to match standalone case. Change-Id: I5f57308a8d9481c98d29a38d3131597dc1383b47
diff --git a/src/main/resources/Documentation/build.md b/src/main/resources/Documentation/build.md index e9e055e..eabf7d3 100644 --- a/src/main/resources/Documentation/build.md +++ b/src/main/resources/Documentation/build.md
@@ -71,6 +71,12 @@ bazel-bin/plugins/@PLUGIN@/@PLUGIN@.jar ``` +To execute the tests run: + +``` + bazel test plugins/@PLUGIN@:@PLUGIN@_tests +``` + This project can be imported into the Eclipse IDE. Add the plugin name to the `CUSTOM_PLUGINS` set in Gerrit core in `tools/bzl/plugins.bzl`, and execute: @@ -79,12 +85,6 @@ ./tools/eclipse/project.py ``` -To execute the tests run: - -``` - bazel test plugins/@PLUGIN@:@PLUGIN@_tests -``` - How to build the Gerrit Plugin API is described in the [Gerrit documentation](../../../Documentation/dev-bazel.html#_extension_and_plugin_api_jar_files).