[jira] (MRELEASE-867) The release:prepare doesn't commit pom.xml changes

["Adrien Lecharpentier (JIRA)" <ji...@codehaus.org>]

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

Adrien Lecharpentier closed MRELEASE-867.
-----------------------------------------

    Resolution: Duplicate

You were right. It is a duplication of MRELEASE-812. I didn't see this issue before.

Adding
{code:xml}
<dependencies>
  <dependency>
    <groupId>org.apache.maven.scm</groupId>
    <artifactId>maven-scm-provider-gitexe</artifactId>
    <version>1.9</version>
  </dependency>
</dependencies>
{code}

to my pom.xml made the job. Thanks!

> The release:prepare doesn't commit pom.xml changes
> --------------------------------------------------
>
>                 Key: MRELEASE-867
>                 URL: https://jira.codehaus.org/browse/MRELEASE-867
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: Git
>    Affects Versions: 2.4.2
>         Environment: Mac, maven-3.2.1, git-1.9.0
>            Reporter: Adrien Lecharpentier
>
> Hi,
> the plugin seems not to commit the changes to the pom when upgrading the version. At first I thought it was the same issue than http://jira.codehaus.org/browse/MRELEASE-830 but in my log, I clearly see that the plugin doesn't commit the files:
> {code}
> [INFO] Executing: /bin/sh -c cd /Users/adrien/***/***-jira && git add -- pom.xml
> [INFO] Working directory: /Users/adrien/***/***-jira
> [INFO] Executing: /bin/sh -c cd /Users/adrien/***/***-jira && git status
> [INFO] Working directory: /Users/adrien/***/***-jira
> [INFO] Tagging release with the label ***-1.0.2...
> [INFO] Executing: /bin/sh -c cd /Users/adrien/***/***-jira && git tag -F /var/folders/z9/chxs95dn61j18jrs0nb18c540000gn/T/maven-scm-1442291122.commit ***-1.0.2
> [INFO] Working directory: /Users/adrien/***/***
> [INFO] Executing: /bin/sh -c cd /Users/adrien/***/***-jira && git push git@github.com:Zenika/codesonar-plugin.git ***-1.0.2
> [INFO] Working directory: /Users/adrien/***/***-jira
> [INFO] Executing: /bin/sh -c cd /Users/adrien/***/***-jira && git ls-files
> [INFO] Working directory: /Users/adrien/***/***-jira
> [INFO] Transforming 'Jenkins CodeSonar Plugin'...
> [INFO] Not removing release POMs
> [INFO] Checking in modified POMs...
> [INFO] Executing: /bin/sh -c cd /Users/adrien/***/***-jira && git add -- pom.xml
> [INFO] Working directory: /Users/adrien/***/***-jira
> [INFO] Executing: /bin/sh -c cd /Users/adrien/***/***-jira && git status
> [INFO] Working directory: /Users/adrien/***/***-jira
> [INFO] Release preparation complete.
> {code}
> First, it add the pom, then do a tag and finally push it. The staged pom is never commit. Which is strange is that the "git status" should tell the plugin that there is a "uncommited changed".
> Thanks.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)