[
https://issues.apache.org/jira/browse/MRELEASE-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-148.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Add prompts to input parent POM release version and next development version
> ----------------------------------------------------------------------------
>
> Key: MRELEASE-148
> URL: https://issues.apache.org/jira/browse/MRELEASE-148
> Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)
