[
https://issues.apache.org/jira/browse/MRELEASE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544338#comment-14544338
]
Robert Scholte commented on MRELEASE-911:
-----------------------------------------
{{release:perform}} has nothing to do with branches. It checks out a _tag_
created by {{release:prepare}} and calls {{mvn deploy}} on the checked out
directory.
What are you trying to do? {{release:branch}} followed by {{release:perform}}?
> release plugin forming incorrect git clone command
> --------------------------------------------------
>
> Key: MRELEASE-911
> URL: https://issues.apache.org/jira/browse/MRELEASE-911
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: Git
> Affects Versions: 2.5.2
> Reporter: sandyzden
>
> git-exe plugin completely ignores the branch parameter and fails in cloning
> the repository during {{release:perform}}
> e.g. git clone --branch <git url> <working dir> this causes it to determine
> the <working dir> as the branch parameter and failing.
> Below is the error message
> {noformat}
> [ERROR] The git-clone command failed.
> [ERROR] fatal: repository '<working dir>/target/checkout' does not exist
> {noformat}
> A bit fiddling on the source code i found out
> {code}
> if ( version != null && ( version instanceof ScmBranch ) )
> {
> cl.createArg().setValue( "--branch" );
> cl.createArg().setValue( version.getName() );
> }
> {code}
> it needed version number, but i was not able to figure how it passed from
> Main Mojo to this class
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
