From dev-return-104696-archive-asf-public=cust-asf.ponee.io@sling.apache.org Wed Mar 18 09:52:45 2020 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 [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 8F8E618025F for ; Wed, 18 Mar 2020 10:52:45 +0100 (CET) Received: (qmail 96327 invoked by uid 500); 18 Mar 2020 09:52:44 -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 96311 invoked by uid 99); 18 Mar 2020 09:52:44 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Mar 2020 09:52:44 +0000 Received: from [10.136.170.127] (unknown [193.105.139.131]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 79E66F8B for ; Wed, 18 Mar 2020 09:52:44 +0000 (UTC) To: dev@sling.apache.org From: Carsten Ziegeler Subject: Version confusion for slingfeature maven plugin Message-ID: <2c0f3eee-4c1e-8371-68c6-227e4e9c8685@apache.org> Date: Wed, 18 Mar 2020 10:52:43 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Hi, in jira I see slingfeature-maven-plugin 1.1.20 https://issues.apache.org/jira/projects/SLING/versions/12347441 as well as OSGi Feature Maven Plugin 1.1.20 https://issues.apache.org/jira/projects/SLING/versions/12347642 We also have OSGi Feature Maven Plugin 1.1.14 open and OSGi Feature Maven Plugin 1.1.12 released On the other hand in the past we released slingfeature-maven-plugin 1.x including a version 1.1.18 and 1.1.14 As we started with slingfeature-maven-plugin (which is also the name of the artifact), I think we should stick with it. Not sure why "OSGi Feature Maven Plugin" was introduced. But regardless, we need to clean up this mess Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziegeler@apache.org