[ 
https://issues.apache.org/jira/browse/NIFIREG-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16119061#comment-16119061
 ] 

ASF GitHub Bot commented on NIFIREG-8:
--------------------------------------

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.


> Define Web REST API 
> --------------------
>
>                 Key: NIFIREG-8
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-8
>             Project: NiFi Registry
>          Issue Type: New Feature
>            Reporter: Kevin Doran
>
> Start to define a  REST Web API that will serve as the contract between 
> clients (e.g., NiFi) and the web service.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to