[
https://issues.apache.org/jira/browse/MINIFI-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15248580#comment-15248580
]
ASF GitHub Bot commented on MINIFI-12:
--------------------------------------
Github user apiri commented on a diff in the pull request:
https://github.com/apache/nifi-minifi/pull/13#discussion_r60306396
--- Diff: pom.xml ---
@@ -177,6 +178,16 @@ limitations under the License.
<version>${org.slf4j.version}</version>
<scope>provided</scope>
</dependency>
+ <dependency>
+ <groupId>org.eclipse.jetty</groupId>
+ <artifactId>jetty-server</artifactId>
+ <version>${jetty.version}</version>
+ </dependency>
+ <dependency>
+ <groupId>org.eclipse.jetty</groupId>
+ <artifactId>jetty-servlet</artifactId>
--- End diff --
Licensing looks okay for Jetty as it is dual licensed EPL & ASLv2, however
there is a NOTICE at
https://github.com/eclipse/jetty.project/blob/master/NOTICE.txt where I think
we need to carry over the copyright in our NOTICE.
> Network based implementation
> ----------------------------
>
> Key: MINIFI-12
> URL: https://issues.apache.org/jira/browse/MINIFI-12
> Project: Apache NiFi MiNiFi
> Issue Type: Sub-task
> Components: Data Format, Management, Processing Configuration
> Reporter: Aldrin Piri
> Assignee: Joseph Percivall
> Fix For: 0.0.1
>
>
> As an initial proof of concept for providing centralized management it would
> be advantageous to have configuration move beyond the file descriptor and
> start happening from "remote" locations. One way of doing this would be via
> simple web service from some control manager to the individual agents. A
> preliminary implementation could make use of a REST service to transmit
> information and harness the work done in MINIFI-2 as the data format to
> transfer the updates to processing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
