From dev-return-93416-archive-asf-public=cust-asf.ponee.io@sling.apache.org Thu Nov 8 22:43:42 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 07B4B180671 for ; Thu, 8 Nov 2018 22:43:41 +0100 (CET) Received: (qmail 43746 invoked by uid 500); 8 Nov 2018 21:43:41 -0000 Mailing-List: contact dev-help@sling.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sling.apache.org Delivered-To: mailing list dev@sling.apache.org Received: (qmail 43733 invoked by uid 99); 8 Nov 2018 21:43:41 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2018 21:43:40 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 7C197C234B for ; Thu, 8 Nov 2018 21:43:40 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 7nNdPoBP7QSg for ; Thu, 8 Nov 2018 21:43:36 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id E00757419B for ; Thu, 8 Nov 2018 16:16:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 83AA8E0F39 for ; Thu, 8 Nov 2018 16:16:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 47088266C1 for ; Thu, 8 Nov 2018 16:16:00 +0000 (UTC) Date: Thu, 8 Nov 2018 16:16:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@sling.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SLING-8032) Add a MOJO which is able to validate JSON Feature file against the JSON Schema MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SLING-8032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16679959#comment-16679959 ] ASF GitHub Bot commented on SLING-8032: --------------------------------------- simonetripodi opened a new pull request #17: SLING-8032 - Add a MOJO which is able to validate JSON Feature file against the JSON Schema URL: https://github.com/apache/sling-slingfeature-maven-plugin/pull/17 ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: users@infra.apache.org > Add a MOJO which is able to validate JSON Feature file against the JSON Schema > ------------------------------------------------------------------------------ > > Key: SLING-8032 > URL: https://issues.apache.org/jira/browse/SLING-8032 > Project: Sling > Issue Type: Improvement > Components: Feature Model, Maven Plugins and Archetypes > Reporter: Simone Tripodi > Assignee: David Bosschaert > Priority: Major > Fix For: slingfeature-maven-plugin 1.0.0 > > > While SLING-7990 contributed the Schema definition, I would like to contribute a simple MOJO which is able to validate Feature files against the Schema. > JSON Schema validation does not fit as an {{AnalyserTask}} implementation, since {{Feature}} instances are parsed already here, anyway the {{Analyser}} takes in charge semantic analysis, while JSON Schema validation is is strict about syntax and structure, this is why I would have a separated MOJO which can be optionally enabled. > PR is coming -- This message was sent by Atlassian JIRA (v7.6.3#76005)