From issues-return-9441-apmail-nifi-issues-archive=nifi.apache.org@nifi.apache.org Wed Sep 21 13:35:12 2016 Return-Path: X-Original-To: apmail-nifi-issues-archive@minotaur.apache.org Delivered-To: apmail-nifi-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0C1AE19E3D for ; Wed, 21 Sep 2016 13:35:12 +0000 (UTC) Received: (qmail 33161 invoked by uid 500); 21 Sep 2016 13:35:12 -0000 Delivered-To: apmail-nifi-issues-archive@nifi.apache.org Received: (qmail 33126 invoked by uid 500); 21 Sep 2016 13:35:11 -0000 Mailing-List: contact issues-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list issues@nifi.apache.org Received: (qmail 33117 invoked by uid 99); 21 Sep 2016 13:35:11 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Sep 2016 13:35:11 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id CBEDADFE61; Wed, 21 Sep 2016 13:35:11 +0000 (UTC) From: pvillard31 To: issues@nifi.apache.org Reply-To: issues@nifi.apache.org References: In-Reply-To: Subject: [GitHub] nifi pull request #1037: NIFI-1893 Add processor for validating JSON Content-Type: text/plain Message-Id: <20160921133511.CBEDADFE61@git1-us-west.apache.org> Date: Wed, 21 Sep 2016 13:35:11 +0000 (UTC) Github user pvillard31 commented on a diff in the pull request: https://github.com/apache/nifi/pull/1037#discussion_r79830777 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/pom.xml --- @@ -249,6 +249,11 @@ language governing permissions and limitations under the License. --> super-csv 2.4.0 + + org.everit.json + org.everit.json.schema + 1.4.0 + --- End diff -- In the pom file, you also have to add the json files you added for testing purpose in order to exclude those files during the rat check (licensing aspects). You can check that everything is fine by running a mvn clean install with the profile contrib-check: ```` mvn clean install -Pcontrib-check ```` Side note: from where are coming the json files your are using for tests? (just to be sure there is no issue) --- 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 infrastructure@apache.org or file a JIRA ticket with INFRA. ---