Github user kevdoran commented on the issue:
https://github.com/apache/nifi-registry/pull/14
@bbende I restructured the modules based on your suggestion. I now have the
following modules:
```
nifi-registry-security // just a container module, packaged
as pom
+--nifi-registry-security-api // gets placed in lib dir for others
to implement against
+--nifi-registry-security-api-impl // NiFi Registry's implementation of
security-api
+--nifi-registry-security-framework // extends registry-framework to add
security
```
Let me know if you agree with this or if it is overkill for what we need.
Technically `nifi-registry-security-api-impl` and
`nifi-registry-security-framework` can be combined (technically, they could
even be part of `nifi-registry-framework`). I can consolidate some of these if
you'd rather keep a flatter, more condensed module structure. Let me know.
---
