From issues-return-138974-archive-asf-public=cust-asf.ponee.io@maven.apache.org Fri Oct 12 20:11:04 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 B7B04180660 for ; Fri, 12 Oct 2018 20:11:03 +0200 (CEST) Received: (qmail 27949 invoked by uid 500); 12 Oct 2018 18:11:02 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 27938 invoked by uid 99); 12 Oct 2018 18:11:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Oct 2018 18:11:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 3B9011A003F for ; Fri, 12 Oct 2018 18:11:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.5 X-Spam-Level: X-Spam-Status: No, score=-109.5 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, NORMAL_HTTP_TO_IP=0.001, 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 (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id rnvwB_kJ7XQZ for ; Fri, 12 Oct 2018 18:11:01 +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 2D9195F3AC for ; Fri, 12 Oct 2018 18:11:01 +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 B5681E0F39 for ; Fri, 12 Oct 2018 18:11: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 781292486A for ; Fri, 12 Oct 2018 18:11:00 +0000 (UTC) Date: Fri, 12 Oct 2018 18:11:00 +0000 (UTC) From: "Carsten Klein (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (MRELEASE-897) support multiple release versions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MRELEASE-897?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 648239#comment-16648239 ]=20 Carsten Klein edited comment on MRELEASE-897 at 10/12/18 6:10 PM: ------------------------------------------------------------------ [~rfscholte] I have additional requirements, e.g. release tags, e.g. FINAL = or RC1 and so on. And also a build number that should be included in the version, e.g. 1.0.0-= FINAL or 1.0.1-RC1-3233. But this is mainly for when building applications that then will be=C2=A0pu= t into docker images and where the docker=C2=A0image will then be tagged us= ing the build number. Or when providing release candidates or even beta or alpha releases for tes= ting. While both beta and alpha releases can be expressed by snapshot relea= ses, release candidates should not. was (Author: silkentrance): [~rfscholte] I have additional requirements, e.g. release tags, e.g. FINAL = or RC1 and so on. And also a build number that should be included in the version, e.g. 1.0.0-= FINAL or 1.0.1-RC1-3233. But this is mainly for when building applications that then will be=C2=A0pu= t into docker images and where the docker=C2=A0image will then be tagged us= ing the build number or when providing release candidates or even beta or a= lpha releases for testing. > support multiple release versions > --------------------------------- > > Key: MRELEASE-897 > URL: https://issues.apache.org/jira/browse/MRELEASE-897 > Project: Maven Release Plugin > Issue Type: Improvement > Reporter: Romain Manni-Bucau > Priority: Major > > In some project multiple versions are used (tomee release =3D tomee + ope= nejb releases for instance). It is not always possible to split the project= in sub projects and then it is not possible to use maven release plugin. I= dea would be to support a whitelist of artifacts (a list of patterns would = be great). > {code} > > org.superbiz.component:*:1.0.1 > org.superbiz.component:*:4.5.8 > > {code} > For instance or even: > {code} > > org.superbiz.component:*:@major.@minor.@patch > org.superbiz.component:*:(@major + 3).@minor.@patch > > {code} > to avoid to change it for each release. > This of course would imply the CLI to ask for the multiple versions and n= ot only one even when autoSubModules is set to true (it would just group by= versions) -- This message was sent by Atlassian JIRA (v7.6.3#76005)