[
https://jira.codehaus.org/browse/MRELEASE-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316420#comment-316420
]
Fred Cooke commented on MRELEASE-815:
-------------------------------------
If, instead of pushing, you fetch, it shows the update to the remote. Likewise,
a git status shows this: Your branch is ahead of 'remotes/origin/master' by 2
commits.
> Local ref for remote not updated by git scm during release
> ----------------------------------------------------------
>
> Key: MRELEASE-815
> URL: https://jira.codehaus.org/browse/MRELEASE-815
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: Git, prepare
> Affects Versions: 2.3.2
> Environment: Debian Linux OpenJDK 7 mvn 3.0.4
> Reporter: Fred Cooke
> Priority: Trivial
> Attachments: mvn.release.fails.to.update.local.ref.for.remote.png
>
>
> When pushing the pom changes during a release prepare the remote itself is
> updated correctly, however the local repositories ref for the remote is not.
> Simply running "git push" on the command line and getting "Everything up to
> date." back remedies the situation, however it'd be nice if mvn didn't leave
> the local git repo "dirty" in this way.
> Screen shot of gitg showing how it LOOKS attached. Reality is not the same.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
