gerrit

History

Dave Borowitz b5b6f615ec Move more functionality from elsewhere into ApprovalsUtil The commonality of these methods is they will have a different implementation when approvals are read from an eventual notedb, so it makes sense to keep them located together. Change-Id: I5de63a4210f29863274111964480fb1f5720ca60		2013-12-19 10:30:56 -08:00
..
commit-message-length-validator@c4ac20cd95	Update core plugin revisions to remove Maven support	2013-12-05 00:32:58 +09:00
cookbook-plugin@9160d607f4	Wait for UI plugins to load	2013-12-10 23:37:13 -08:00
download-commands@6287d6a894	Move "refs/..." constants to a RefNames class	2013-12-11 12:41:07 -08:00
replication@330228ed74	Move "refs/..." constants to a RefNames class	2013-12-11 12:41:07 -08:00
reviewnotes@0b0419b4aa	Move more functionality from elsewhere into ApprovalsUtil	2013-12-19 10:30:56 -08:00
singleusergroup@c9ad9d1be4	Add singleusergroup plugin	2013-11-09 07:45:00 +01:00
BUCK	Buck: Fix infinite loop when trying to build non-existing core plugins	2013-12-16 16:26:26 +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.