You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joshua Spiewak (JIRA)" <ji...@codehaus.org> on 2014/03/18 16:51:59 UTC
[jira] (MRELEASE-839) Unable to supply tag to release for
release:perform
[ https://jira.codehaus.org/browse/MRELEASE-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343155#comment-343155 ]
Joshua Spiewak commented on MRELEASE-839:
-----------------------------------------
I think the problem may be that the other mojos were all updated to extend the new {{AbstractScmReleaseMojo}} while {{PerformReleaseMojo}} still extends {{AbstractReleaseMojo}}. Thus {{mvn release:perform}} does not have access to the tag that is passed in, and the git scm provider tries to run {{git clone --branch <repo> <directory>}}. Since the tag is missing from the command, you get an error:
{noformat}
[ERROR] The git-clone command failed.
[ERROR] Command output:
[ERROR] fatal: repository '/Users/jspiewak/work/bc/mrptest/target/checkout' does not exist
{noformat}
This is still an issue with 2.5
> Unable to supply tag to release for release:perform
> ---------------------------------------------------
>
> Key: MRELEASE-839
> URL: https://jira.codehaus.org/browse/MRELEASE-839
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.4.1
> Reporter: Tuure Laurinolli
>
> The documentation at http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html and http://maven.apache.org/maven-release/maven-release-plugin/plugin-info.html claims that releases can be ma de of a specific tag, but no mechanism for this is specified.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)