[
https://jira.codehaus.org/browse/MRELEASE-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MRELEASE-226.
---------------------------------
Resolution: Duplicate
release:branch exists already
> Provide an option to create a branch for maintenance releases
> -------------------------------------------------------------
>
> Key: MRELEASE-226
> URL: https://jira.codehaus.org/browse/MRELEASE-226
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: branch
> Environment: All
> Reporter: Jim Crossley
>
> This email thread prompted this issue:
> http://www.mail-archive.com/[email protected]/msg65485.html
> As I [Heinrich Nirschl] see it there are two solutions:
> 1) starting the maintenance branch before the release and doing the
> release on the branch, in this case you have to manually adjust the
> version on the trunk.
> 2) doing the release on the trunk and starting the maintenance branch
> from the tagged version, in this case the version has to be manually
> updated on the branch.
> Both approaches work, but there is some manual version editing in
> both. Once the branching is done, the release plugin works fine on the
> branch (for releasing further maintenance releases) and on the trunk
> (for releasing the next major release). The manual update is only
> necessary once per branch.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
