[
http://jira.codehaus.org/browse/MRELEASE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Kramer closed MRELEASE-580.
---------------------------------
Resolution: Duplicate
Fix Version/s: 2.0
Found out a plugin that we were using was forcing v1.1 of the scm plugin to be
brought in.
> Can't release when on branch using git
> --------------------------------------
>
> Key: MRELEASE-580
> URL: http://jira.codehaus.org/browse/MRELEASE-580
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.0-beta-8
> Environment: linux, Fedora 13, x86_64, using sun java 1.6.0_14
> Reporter: Brian Kramer
> Fix For: 2.0
>
>
> After creating a bug fix branch in git we can't perform a release on the
> branch. The release:prepare works just fine, but the release:perform doesn't
> checkout the branch to build.
> Steps taken:
> git checkout -b bug_fix_branch
> ...Make necessary changes...
> git push
> mvn release:prepare
> mvn release:perform
> When the clone on the perform action occurs it clones "master" and not
> "bug_fix_branch" and then subsequently pulls in changes from the tag that was
> created that aren't valid for master, which has since moved forward.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
