[
https://issues.apache.org/jira/browse/MRELEASE-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16591360#comment-16591360
]
Robert Scholte commented on MRELEASE-933:
-----------------------------------------
bq. why is this still not fixed ....
AFAIK there's still no test to confirm this issue and there's no patch to fix
it.
bq. and why is the latest release almost 3 years old (Oktober 2015)?
This plugin seems in good condition, while a small team of volunteers is
working on one of the other 90+ subprojects of Maven.
bq. it seems like there is some quite recent activity in the project
GitHub/[Gitbox|https://gitbox.apache.org/repos/asf?p=maven-release.git]!?
Activities are mainly related to increasing coverage of OS/JDK/Maven
combinations and to fix support of Java 7.
I have started a redesign of the plugin, to make it more flexible. However,
other more important topics came by (Java9+, Maven 3.5.x) so I had to move that
aside.
In other words: any help is appreciated! See also
http://maven.apache.org/guides/development/guide-helping.html
> 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
> Priority: Major
>
> 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 g...@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
(v7.6.3#76005)
