Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Date: Fri, 8 Nov 2013 11:53:52 -0600 (CST)
From: "Robert Scholte (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Message-ID: 
 <JIRA.145914.1367764287899.33163.1383933232981@codehaus01.managed.contegix.com>
In-Reply-To: <JIRA.145914.1367764287899@codehaus01.managed.contegix.com>
References: <JIRA.145914.1367764287899@codehaus01.managed.contegix.com>
Subject: [jira] (MRELEASE-837) Release plugin resets parent to outdated
 version
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


     [ https://jira.codehaus.org/browse/MRELEASE-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MRELEASE-837.
-----------------------------------

    Resolution: Cannot Reproduce
      Assignee: Robert Scholte

Already fixed in a previous version.
                
> Release plugin resets parent to outdated version
> ------------------------------------------------
>
>                 Key: MRELEASE-837
>                 URL: https://jira.codehaus.org/browse/MRELEASE-837
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0
>            Reporter: Markus KARG
>            Assignee: Robert Scholte
>            Priority: Critical
>
> Using Maven 3.0.4 I noticed that the release plugin resets the parent to an outdated version. Here is what I noticed with all of my Projects when doing "mvn release:prepare":
> * Asks whether I want to update the parent version. I say "yes".
> * Asks whether "1.1" is the correct release version of paren, which is true.
> * Asks whether "1.2-SNAPSHOT" is the correct developer version of parent, which is true.
> * Asks whether "1.1" is the correct release version of child, which is true.
> * Asks whether "1.2-SNAPSHOT" is the correct developer version of child, which is true.
> After perform is done, my pom has different versions for parent and child:
> * Child correctly has "1.2-SNAPSHOT"
> * Parent incorrectly is reset to "1.1-SNAPSHOT"
> This is simple to fix in each POM, but annoying when releasing much and often. Hence I would be glad if this could get fixed soon.

--
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