[
https://jira.codehaus.org/browse/MRELEASE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly closed MRELEASE-170.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.2
<cheeky>I am going to claim that this is fixed in 2.2</cheeky>
Please re-open if it is not actually fixed ;-)
Here is my claim:
Use
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#completionGoals
to run release:branch with
http://maven.apache.org/plugins/maven-release-plugin/branch-mojo.html#updateWorkingCopyVersions=false
and
http://maven.apache.org/plugins/maven-release-plugin/branch-mojo.html#updateBranchVersions=true
configured in your pom.
> Create a branch during prepare
> ------------------------------
>
> Key: MRELEASE-170
> URL: https://jira.codehaus.org/browse/MRELEASE-170
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Components: scm
> Reporter: Jonathan Komorek
> Priority: Minor
> Fix For: 2.2
>
>
> It is typical with some of my projects that as I'm cutting the release I am
> already thinking about the next patch. In other words, creating a branch to
> allow patching of a release is a part of my release process.
> I would like a way to create a branch during the prepare goal of a release.
> For instance, if I'm releasing 4.0-SNAPSHOT I would like to create a 4.0 tag
> as is currently done, but also a 4.0.1-SNAPSHOT branch.
> Please note that I have recently migrated from CVS / ANT to SVN / Maven so
> I'm open to alternatives from someone with more experience on these
> platforms. Although I have not written any code for a Maven plugin
> previously, I would be willing to make these additions myself if nobody minds
> and I can get someone to review my code - the experience would help me better
> understand Maven and this plugin in particular.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
