Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1B822200B6C for ; Sun, 28 Aug 2016 11:09:30 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 19E5F160AB4; Sun, 28 Aug 2016 09:09:30 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 63BA4160AAF for ; Sun, 28 Aug 2016 11:09:29 +0200 (CEST) Received: (qmail 42581 invoked by uid 500); 28 Aug 2016 09:09:27 -0000 Mailing-List: contact dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Developers List" Reply-To: "Maven Developers List" Delivered-To: mailing list dev@maven.apache.org Received: (qmail 42559 invoked by uid 99); 28 Aug 2016 09:09:27 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Aug 2016 09:09:27 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 993D7C142C for ; Sun, 28 Aug 2016 09:09:26 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3 X-Spam-Level: *** X-Spam-Status: No, score=3 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id CR-BDMWa2d2b for ; Sun, 28 Aug 2016 09:09:26 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D8C105FADB for ; Sun, 28 Aug 2016 09:09:25 +0000 (UTC) Received: from static.162.255.23.22.macminivault.com (unknown [162.255.23.22]) by mbob.nabble.com (Postfix) with ESMTP id B0E492FCCAF9 for ; Sun, 28 Aug 2016 02:08:59 -0700 (PDT) Date: Sun, 28 Aug 2016 02:09:24 -0700 (MST) From: Tibor Digana To: dev@maven.apache.org Message-ID: In-Reply-To: References: <57BCCDD9.3040900@schulte.it> <11158675.IHDJzPLB6T@herve-desktop> <1586428.57WuyZLAhA@herve-desktop> Subject: Re: POM Model version 4.1.0 in 3.4.0-SNAPSHOTs MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_17792_1819818182.1472375364754" archived-at: Sun, 28 Aug 2016 09:09:30 -0000 ------=_Part_17792_1819818182.1472375364754 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Robert, as I am reading your comments, I see the situation is not be so tragic :) What about to let m-deploy-p and m-release-p to decide on modelVersion of consumer project as the minimum version. If for instance a new scope value is available in of your project POM, then the plugin would decide to align modelVersion to higher than 4.0 and lower or equal to modelVersion in reactor's parent POM. This would guarantee that the consumer POM has minimum conflicts and maximize consumers community who can use this POM from Maven Central To override the modelVersion in Consumer POM: -- Cheers Tibor -- View this message in context: http://maven.40175.n5.nabble.com/Re-POM-Model-version-4-1-0-in-3-4-0-SNAPSHOTs-tp5878254p5878961.html Sent from the Maven Developers mailing list archive at Nabble.com. ------=_Part_17792_1819818182.1472375364754--