From issues-return-86985-apmail-maven-issues-archive=maven.apache.org@maven.apache.org Sat Sep 14 11:36:24 2013 Return-Path: X-Original-To: apmail-maven-issues-archive@minotaur.apache.org Delivered-To: apmail-maven-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 3D8DE1093D for ; Sat, 14 Sep 2013 11:36:24 +0000 (UTC) Received: (qmail 14923 invoked by uid 500); 14 Sep 2013 11:36:22 -0000 Delivered-To: apmail-maven-issues-archive@maven.apache.org Received: (qmail 14713 invoked by uid 500); 14 Sep 2013 11:36:20 -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 14696 invoked by uid 99); 14 Sep 2013 11:36:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Sep 2013 11:36:17 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [199.193.192.100] (HELO codehaus01.managed.contegix.com) (199.193.192.100) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Sep 2013 11:36:13 +0000 Received: from codehaus01 (localhost.localdomain [127.0.0.1]) by codehaus01.managed.contegix.com (Postfix) with ESMTP id E6059B10DC for ; Sat, 14 Sep 2013 06:35:52 -0500 (CDT) Date: Sat, 14 Sep 2013 06:35:52 -0500 (CDT) From: "Robert Scholte (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] (MRELEASE-431) Configuration of policy for calculating next (release) version MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 22cf62d5d84cf5bea94eb3b65e0ebd09 X-Virus-Checked: Checked by ClamAV on apache.org [ https://jira.codehaus.org/browse/MRELEASE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332812#comment-332812 ] Robert Scholte commented on MRELEASE-431: ----------------------------------------- [~simonetripodi] asked me to give some feedback. I have some other stuff which need to be released first. I still have to decide if we should introduce a separate project for the versionPolicyManager or include it as a module of the Maven Release project. Another thing on my mind: should the API support methods to make it a major, minor or bugversion increase, or leave that up to the implementation ( which should be verify easy with the {{implementation=""}} trick)? Since we're talking about an API which will stay forever, we need the time to make the right decisions. > Configuration of policy for calculating next (release) version > -------------------------------------------------------------- > > Key: MRELEASE-431 > URL: https://jira.codehaus.org/browse/MRELEASE-431 > Project: Maven Release Plugin > Issue Type: New Feature > Components: prepare > Affects Versions: 2.0-beta-8 > Reporter: Carsten Ziegeler > Assignee: Robert Scholte > Fix For: 2.5 > > Attachments: 0001-MRELEASE-431-Configuration-of-policy-for-calculating.patch, MRELEASE-431.patch, MRELEASE-431-v2.patch > > > Currently, when preparing the release, the version to release is always the next version which usually is the current version without the snapshot extension. > There are quiet a lot projects (Apache Felix, Sling and others) following an even release numbering policy. So while the current development version is odd (like 1.2.3-SNAPSHOT), the next released version will be 1.2.4. > It would be nice if this could be made configuration through some configuration property like > next-even (with possible values being: next (default, as-is), next-even, next-odd > I briefly scanned through the code and it seems that adding support for this requires changes in both, the release-manager and the release-plugin. > If this feature gets accepted and if someone could give me some minor hints how/where to add this I could come up with a patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira