opendev/gerrit
Code Issues Proposed changes

Merge branch 'stable-2.15' into stable-2.16

Browse Source 
* stable-2.15:
  Change wording about the example plugin in dev-plugins.txt
  Remove references to cookbook plugin from dev-eclipse.txt

Change-Id: Iaa4f81f6c6406631ca149c21ad81e015b348a21e
This commit is contained in:
David Pursehouse
2019-04-26 10:22:18 +09:00
parent 29153205fd 092ac5c201
commit 90569bd1fb
2 changed files with 7 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
Documentation/dev-eclipse.txt
View File

@@ -147,17 +147,17 @@ in the SDM debug session.
`codeserver` needs two additional inputs to expose the plugin module in the SDM
debug session: the module name and the source folder location. For example the
module name and source folder of `cookbook-plugin` should be added in the local
module name and source folder of any GWT plugin should be added in the local
copy of the `gerrit_gwt_debug` configuration:
----
com.googlesource.gerrit.plugins.cookbook.HelloForm \
-src ${resource_loc:/gerrit}/plugins/cookbook-plugin/src/main/java \
com.googlesource.gerrit.plugins.myplugin.HelloForm \
-src ${resource_loc:/gerrit}/plugins/myplugin/src/main/java \
-- --console-log [...]
----
After doing that, both the Gerrit core and plugin GWT modules can be activated
during SDM (debug session)[http://imgur.com/HFXZ5No].
during SDM (debug session).
GERRIT
------

9
Documentation/dev-plugins.txt
View File

@@ -33,12 +33,9 @@ Most of this documentation refers to either type as a plugin.
[[getting-started]]
== Getting started
To get started with the development of a plugin clone the sample
plugins:
----
$ git clone https://gerrit.googlesource.com/plugins/examples
----
To get started with the development of a plugin, take a look at
the samples in the
link:https://gerrit.googlesource.com/plugins/examples[examples plugin project].
This is a project that demonstrates the various features of the
plugin API. It can be taken as an example to develop an own plugin.