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

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

GitHub user bbende opened a pull request:

    https://github.com/apache/nifi-registry/pull/3

    NIFIREG-6 Adding nifi-registry-bootstrap module

    - Enables registry to have the same setup as NiFi where a bootstrap process 
is started first which launches the main process
    - All the standard operations such as start, stop, dump, etc, should now 
work from nifi-registry.sh
    - Added placeholder LICENSE and NOTICE files to the assembly, need to fill 
in later
    - Create nifi-registry-utils to hold utility code

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bbende/nifi-registry NIFIREG-6

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi-registry/pull/3.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3
    
----
commit 10857d551cc48b67e5188a059406bd045c19bce7
Author: Bryan Bende <[email protected]>
Date:   2017-08-01T18:59:47Z

    NIFIREG-6 Adding nifi-registry-bootstrap module

----


> Add nifi-registry-bootstrap module
> ----------------------------------
>
>                 Key: NIFIREG-6
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-6
>             Project: NiFi Registry
>          Issue Type: Improvement
>    Affects Versions: 0.0.1
>            Reporter: Bryan Bende
>            Assignee: Bryan Bende
>            Priority: Minor
>
> Currently NiFiRegistry is the entry point of the application, and in its 
> current state the main method starts a new Jetty server every time.  
> We should take a similar approach to NiFi where we have a bootstrap process 
> that launches and communicates with the application process.



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

Reply via email to