Peter Kronenberg created MRELEASE-1065:
------------------------------------------
Summary: Workflow for maven-release-plugin for creating new
release in branch
Key: MRELEASE-1065
URL: https://issues.apache.org/jira/browse/MRELEASE-1065
Project: Maven Release Plugin
Issue Type: Improvement
Reporter: Peter Kronenberg
Hi, hope this is the right place for questions
I'm trying to figure out the proper workflow for creating a new release in a
branch, but still setting the current branch for new development
Assuming I'm currently at release 1.0.5-SNAPSHOT. If I do `mvn
release:prepare`, it correctly updates the version to 1.0.5, tags it, and then
sets up for new development with 1.0.6-SNAPSHOT.
I want to do something similar with a new branch instead of tagging. My
expectation would be the new branch would get 1.0.5 and the current branch
would get 1.0.6-SNAPSHOT
Using the command
```
mvn release:branch -DbranchName=1.0.5 -DreleaseVersion=1.0.5
```
I've tried variations of `-DupdateBranchVersions` and
`-DupdateWorkingCopyVersions`. It doesn't appear to do what I want. I also
can't seem to get `-DupdateVersionsToSnapshot=false` to work. It insists on
naming the branch with Snapshot
Is there any way to do this?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
