[jira] [Comment Edited] (MRELEASE-933) maven-release-plugin:perform from a tag is broken for Git in version 2.5.3

["Eric Leventhal Arthen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MRELEASE-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056618#comment-15056618 ] 

Eric Leventhal Arthen edited comment on MRELEASE-933 at 12/14/15 8:02 PM:
--------------------------------------------------------------------------

This is after a release:prepare.

In the pom pluginManagement section where we list maven-release-plugin the one additional thing added as part of that is:
{code}
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-release-plugin</artifactId>
    <version>2.3.2</version> 
    <configuration>
        <!-- Using install:install to overwrite the clover-fied jar
             that is put into the local repository from the sonar:sonar goal -->
        <goals>deploy sonar:sonar install:install</goals>
        <useReleaseProfile>false</useReleaseProfile>
    </configuration>
</plugin>
{code}

Are there other dependencies or plugin versions that we should make sure are at particular versions?

Here are some other possibly related plugins we specify, I don't know if any of these are relevant.
{code}
org.apache.maven.plugins; maven-resources-plugin; 2.5
org.apache.maven.plugins; maven-jar-plugin; 2.3.2
org.codehaus.mojo; sonar-maven-plugin; 2.6
org.apache.maven.plugins; maven-deploy-plugin; 2.7
org.apache.maven.plugins; maven-assembly-plugin; 2.2.1
{code}


was (Author: earthen):
This is after a release:prepare.

In the pom pluginManagement section where we list maven-release-plugin the one additional thing added as part of that is:
{code}
org.apache.maven.plugins; maven-release-plugin; 2.3.2  <!-- 2.5.3 'perform' command fails... -->
    <configuration>
        <!-- Using install:install to overwrite the clover-fied jar
             that is put into the local repository from the sonar:sonar goal -->
        <goals>deploy sonar:sonar install:install</goals>
        <useReleaseProfile>false</useReleaseProfile>
    </configuration>
{code}

Are there other dependencies or plugin versions that we should make sure are at particular versions?

Here are some other possibly related plugins we specify, I don't know if any of these are relevant.
{code}
org.apache.maven.plugins; maven-resources-plugin; 2.5
org.apache.maven.plugins; maven-jar-plugin; 2.3.2
org.codehaus.mojo; sonar-maven-plugin; 2.6
org.apache.maven.plugins; maven-deploy-plugin; 2.7
org.apache.maven.plugins; maven-assembly-plugin; 2.2.1
{code}

> maven-release-plugin:perform from a tag is broken for Git in version 2.5.3
> --------------------------------------------------------------------------
>
>                 Key: MRELEASE-933
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-933
>             Project: Maven Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.5
>            Reporter: Eric Leventhal Arthen
>
> We are also blocked from using {{maven-release-plugin:2.5:perform}} for Git releases because it no longer passes in the tag name so the "git clone" fails.
> This worked correctly in {{maven-release-plugin:2.3.2:perform}}, with that version we got a command like this:
> {noformat}
>     git clone --branch my-base-1.4.6 git@bithub:abcde/fghij.git /home/buildacct/work/5f89075470257ef1/base/target/checkout
> {noformat}
> (Note that the name here is (correctly) a tag name created by release:prepare, even though it is passed to --branch.)
> With {{maven-release-plugin:2.5:perform}} it does not include the actual tag name after "--branch" so the command fails.
> {noformat}
>     git clone --branch git@bithub.brightcove.com:abcde/fghij.git /home/buildacct/work/7483cd6cc5ce81ea/target/checkout
>    [ERROR] The git-clone command failed.
> {noformat}
> We have to downgrade to the older maven-release-plugin, 2.3.2. From the ticket below this also worked in 2.2.1. I have not tried other versions.
> Found a description of this problem in SCM-729 in a comment in Feb 2015, but are creating this ticket because the issue is a recently introduced bug and that ticket is a feature request for a different component.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)