gerrit/plugins
David Pursehouse ca1e88f882 Set correct revision of cookbook plugin
Commit bcee7ff updated the plugin to revision abba494, but that was not
based on the head of the branch and resulted in a merge commit when it
was submitted.  Thus, the revision set on the plugin was not the latest
on the branch.

Set it to the correct revision.

Change-Id: I421c73fefcf382dd84780e09b5e05b3b20413655
2015-10-30 11:29:26 +09:00
..
commit-message-length-validator@7923b67392 Update plugins 2014-10-31 18:19:48 +09:00
cookbook-plugin@0f50526955 Set correct revision of cookbook plugin 2015-10-30 11:29:26 +09:00
download-commands@63e7cf5f24 Update download-commands plugin revision 2015-06-30 14:16:27 +02:00
replication@af5edf6047 Update replication plugin 2015-10-14 15:13:22 +09:00
reviewnotes@f6403a1ed3 Update reviewnotes plugin to latest revision 2015-06-10 21:20:19 +09:00
singleusergroup@691c9c9c4f Update singleusergroup to latest revision 2015-10-08 10:56:36 -04:00
BUCK Buck: Make deps to $(exe :foo) and $(location :bar) implicitly 2014-06-10 07:29:42 +00:00
README Ensure core plugins are bundled by Maven 2013-05-06 15:36:46 -07:00

If you are adding a directory here:

- Search all pom.xml files for "CORE PLUGIN LIST".
- Add the new plugin to that location.
- (optional) Thank the Maven developers for making this easy.

- Ensure the plugin's pom.xml <version> is the same as Gerrit's
  own pom.xml(s). Gerrit will only embed a plugin that has the
  same version as itself.

- Register the plugin as a submodule with git submodule.