Github user bbende commented on the issue:
https://github.com/apache/nifi-registry/pull/4
@kevdoran this looks great....
Running a full build I ran into an error when the swagger plugin was
running, I had to change the config in the pom to wrap the locations and
schemes in sub-elements like this:
```
<locations>
<location>org.apache.nifi.registry.web.api</location>
</locations>
<schemes>
<scheme>http,https</scheme>
</schemes>
```
Not sure why I would run into that and you wouldn't. I'm using Maven 3.3.3,
but the version of the plugin should be the same for both of us?
Other minor point, running with -Pcontrib-check there are some failures
related to using wildcard imports. The current rules are just a copy from NiFi.
Anyway, I have the changes made for both of these if you want me to just
include them when I merge it in, but I wanted to check about the plugin just to
make sure I wouldn't be screwing up something else by changing that. Let me
know what you think.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
