Documentation: Refactor Eclipse related sections Move standalone Eclipse IDE import section from in-tree to standalone section. Move in-tree Eclipse IDE import after in-tree testing to match other plugins. Change-Id: Ieaba9f330f494c3cc1a6d524de0cb93c611b283f
diff --git a/src/main/resources/Documentation/build.md b/src/main/resources/Documentation/build.md index e59c128..5bd6251 100644 --- a/src/main/resources/Documentation/build.md +++ b/src/main/resources/Documentation/build.md
@@ -25,6 +25,14 @@ bazel test //... ``` +This project can be imported into the Eclipse IDE. Execute: + +``` + ./tools/eclipse/project.sh +``` + +to generate the required files and then import the project. + ### Build in Gerrit tree Put the external dependency Bazel build file into the Gerrit /plugins directory, @@ -48,14 +56,6 @@ bazel-bin/plugins/@PLUGIN@/@PLUGIN@.jar ``` -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: - -``` - ./tools/eclipse/project.py -``` - To execute the tests run either one of: ``` @@ -63,14 +63,14 @@ bazel test plugins/@PLUGIN@:@PLUGIN@_tests ``` -This project can be imported into the Eclipse IDE. Execute: +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: ``` - ./tools/eclipse/project.sh + ./tools/eclipse/project.py ``` -to generate the required files and then import the project. - How to build the Gerrit Plugin API is described in the [Gerrit documentation](../../../Documentation/dev-bazel.html#_extension_and_plugin_api_jar_files).