Add specific exception to signal invalid code owner config files

At the moment an invalid code owner config file results in a
ConfigInvalidException.

Replace this with the custom InvalidCodeOwnerConfigException:

* ConfigInvalidException can also occur due to other reasons, having a
  specific exception allows to better distinguish exceptions caused by
  invalid code owner config file from exceptions caused by other
  reasons.

* This will allow us to store additional information in the exception,
  e.g. the name of the project/branch that contains the invalid code
  owner file (we need this for a follow-up change).

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I42a8f84cf883ef9b443e75fcb538fa707ce72cc6
9 files changed
tree: 5d3c6aaabcf7451ad2be3a356dd763869fe84336
  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.