Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1576#discussion_r110553363
--- Diff:
nifi-nar-bundles/nifi-morphlines-bundle/nifi-morphlines-processors/pom.xml ---
@@ -0,0 +1,110 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+ http://www.apache.org/licenses/LICENSE-2.0
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<project xmlns="http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
+ <modelVersion>4.0.0</modelVersion>
+
+ <parent>
+ <groupId>org.apache.nifi</groupId>
+ <artifactId>nifi-morphlines-bundle</artifactId>
+ <version>1.2.0-SNAPSHOT</version>
+ </parent>
+
+ <artifactId>nifi-morphlines-processors</artifactId>
+ <packaging>jar</packaging>
+
+ <dependencies>
+ <dependency>
+ <groupId>org.apache.nifi</groupId>
+ <artifactId>nifi-api</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.apache.nifi</groupId>
+ <artifactId>nifi-processor-utils</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.apache.nifi</groupId>
+ <artifactId>nifi-mock</artifactId>
+ <scope>test</scope>
+ </dependency>
+ <dependency>
+ <groupId>org.slf4j</groupId>
+ <artifactId>slf4j-simple</artifactId>
+ <scope>test</scope>
+ </dependency>
+ <dependency>
+ <groupId>junit</groupId>
+ <artifactId>junit</artifactId>
+ <version>4.11</version>
+ <scope>test</scope>
+ </dependency>
+ <dependency>
+ <groupId>org.kitesdk</groupId>
+ <artifactId>kite-morphlines-core</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.kitesdk</groupId>
+ <artifactId>kite-morphlines-avro</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.kitesdk</groupId>
+ <artifactId>kite-morphlines-json</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.kitesdk</groupId>
+ <artifactId>kite-morphlines-saxon</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.kitesdk</groupId>
+ <artifactId>kite-morphlines-hadoop-core</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.kitesdk</groupId>
+ <artifactId>kite-morphlines-hadoop-parquet-avro</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.kitesdk</groupId>
+ <artifactId>kite-morphlines-hadoop-sequencefile</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.kitesdk</groupId>
+ <artifactId>kite-morphlines-hadoop-rcfile</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.kitesdk</groupId>
+ <artifactId>kite-morphlines-tika-core</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.kitesdk</groupId>
+ <artifactId>kite-morphlines-tika-decompress</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.kitesdk</groupId>
+ <artifactId>kite-morphlines-twitter</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.kitesdk</groupId>
+ <artifactId>kite-morphlines-maxmind</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.kitesdk</groupId>
+ <artifactId>kite-morphlines-metrics-servlets</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.kitesdk</groupId>
+ <artifactId>kite-morphlines-useragent</artifactId>
--- End diff --
I'm a bit worried that importing all of these dependencies is a too broad
in scope. From my understanding not all of them are inherently needed but
instead represent a toolbox of things that could potentially be used.
I'd much prefer we limit this to a core group of functionality that we
can't already do in NiFi instead.
---
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.
---
