You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2016/01/12 21:12:46 UTC

[jira] [Closed] (MRELEASE-815) Local ref for remote not updated by git scm during release

     [ https://issues.apache.org/jira/browse/MRELEASE-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MRELEASE-815.
-----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still persists, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> Local ref for remote not updated by git scm during release
> ----------------------------------------------------------
>
>                 Key: MRELEASE-815
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-815
>             Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)