gerrit

Files

David Pursehouse 1164e53283 Allow to add custom core plugins in release build

Add a new CUSTOM list in the plugins BUCK config, which is by
default empty. This allows a cleaner patch when adding custom
plugins to be included as 'core' in the release build of a
forked Gerrit.

Change-Id: I12783a8222550983e65bf3bbcd8aef08cdcc9bed

2015-12-14 19:25:49 +09:00

commit-message-length-validator @ 8d295ed48e

Update commit-message-length-validator plugin to latest revision

2015-05-19 17:35:58 +09:00

cookbook-plugin @ 82eefc2048

Update cookbook plugin revision

2015-10-30 12:01:27 +09:00

download-commands @ 87075138f5

Update download-commands plugin

2015-11-19 13:40:07 +09:00

replication @ 675d9dd370

Update replication plugin with merge from stable-2.11

2015-11-12 17:53:46 -08:00

reviewnotes @ 26f38c4514

Open Repository and RevWalk in try-with-resource

2015-08-27 18:40:14 +09:00

singleusergroup @ f6df7121d2

Merge branch 'stable-2.11'

2015-10-09 16:07:35 +09:00

BUCK

Allow to add custom core plugins in release build

2015-12-14 19:25:49 +09:00

README

Ensure core plugins are bundled by Maven

2013-05-06 15:36:46 -07:00

README

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.