Split monolithic plugin target across java packages

It's a left over from GWT plugin era to produce single target library
for all plugin sources. Now, that GWT UI was removed, this restriction
does not exist any more.

Splitting the Bazel packages across java packages has a number of
advantages:

* Reduce re-build time
* Prevention of unwanted interdependences between java packages

Note though, that gerrit_plugin() still doesn't support empty source
set, so that module package of this plugin is still provided as source
set.

Also-by: David Ostrovsky <david@ostrovsky.org>
Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I2886bc319ce31821118416d8b9d8f8e087756b30
21 files changed
tree: 6b1bd0159fce4fe9ffd2b202b5c094b58910bdd3
  1. java/
  2. javatests/
  3. proto/
  4. resources/
  5. test/
  6. ui/
  7. .eslintrc.json
  8. .gitignore
  9. .gitreview
  10. bower.json
  11. BUILD
  12. LICENSE
  13. package-lock.json
  14. package.json
  15. README.md
README.md

Gerrit Code Review code-owners plugin

This plugin provides support for defining code owners for files in a repository.

If the code-owners plugin is enabled, changes can only be submitted if all touched files are covered by approvals from code owners.

Also see resources/Documentation/about.md

IMPORTANT: Before installing/enabling the plugin follow the instructions from the setup guide, see resources/Documentation/setup-guide.md