30c6f47909
Extension panels are embedded in Gerrit screens. To be able to display useful extra information they need access to the object that is being displayed by the Gerrit screen. E.g. for a SettingsScreen the extension panel should have access to the AccountInfo entity of the user. As a first step AccountInfo is provided for the extension points in the SettingsScreen's. To make this work the AccountInfo class must be in a package that is both visible to the Gerrit client and the plugins. Making other *Info classes visible to plugins is more difficult since they partly depend on classes in gerrit-reviewdb which are not visible to plugins. The change in the cookbook plugin shows how the AccountInfo can be accessed in a plugin. Change-Id: Ie285d701ab5860c2a01211ca67d1f77324537303 Signed-off-by: Edwin Kempin <edwin.kempin@sap.com>
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.