jira-importer commented on issue #663: URL: https://github.com/apache/maven-scm/issues/663#issuecomment-2964612019
**[Martin Vysny](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=m.vysny)** commented My mercurial knowledge is limited, but I toyed with branches a bit and this is what I found out: To create a branch, just issue "hg branch \<branch-name>". This creates a branch but does not commit anything - to commit the branch creation just issue hg ci -m "message". This branch creation has one "side effect": the current repository copy is automatically switched to the branch foo. To go back to 'trunk' just issue "hg up default". To go to the branch just issue "hg up foo". To merge from branch foo just switch to trunk "hg up default", merge the files by performing "hg merge foo" and then commit the merge: hg ci -m "message". So, in order to perform mvn release:branch correctly (with default settings - create a branch from current trunk and then update version on trunk) you need to perform: 1. create and commit the branch hg branch \<branchName> hg ci -m "[maven-release-plugin] Branch \<branchName> created" 2. now switch back to trunk hg up default \<increase versions in pom.xml> 1. optionally you may push changes to a server: #hg push \<scmUrl> To check that everything went okay: There should be a new branch visible when issuing "hg branches". The branch should be marked as \<inactive>. Hope this helps. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
