You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Arnaud Heritier (JIRA)" <ji...@codehaus.org> on 2008/12/19 11:26:19 UTC

[jira] Updated: (MRELEASE-148) Add prompts to input parent POM release version and next development version

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

Arnaud Heritier updated MRELEASE-148:
-------------------------------------

    Component/s: prepare

> Add prompts to input parent POM release version and next development version
> ----------------------------------------------------------------------------
>
>                 Key: MRELEASE-148
>                 URL: http://jira.codehaus.org/browse/MRELEASE-148
>             Project: Maven 2.x Release Plugin
>          Issue Type: New Feature
>          Components: prepare
>            Reporter: Eric Berry
>            Priority: Minor
>
> We have a master POM file that we use as a parent for all our other POM that I always release build first.  It is annoying to modify the child POM to reference the new released parent POM version before I do the release and afterwards to set the next  parent POM version.  
> The child POMs are NOT included as a module in the parent POM.  
> The plugin currently works as expected when the child POM references the parent POM and the parent POM references the child POM and you run the release from the parent POM.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira