[
https://jira.codehaus.org/browse/SCM-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte moved MRELEASE-624 to SCM-662:
---------------------------------------------
Complexity: Intermediate
Component/s: (was: perform)
maven-scm-provider-git
Affects Version/s: (was: 2.1)
1.6
Key: SCM-662 (was: MRELEASE-624)
Project: Maven SCM (was: Maven 2.x Release Plugin)
> Performing a release with localCheckout fail on Windows
> -------------------------------------------------------
>
> Key: SCM-662
> URL: https://jira.codehaus.org/browse/SCM-662
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.6
> Environment: Windows Vista, msysgit, Maven 3.0.0
> Reporter: Daniel Spilker
> Assignee: Mark Struberg
> Priority: Minor
> Attachments: GitScmProviderRepository.patch
>
>
> When trying to perform a release on a Windows machine with localCheckout set
> to true, I get the following error message. The path
> 'C:\Users\daspilker\workspaces\myproject' is a git repository.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.1:perform (default-cli) on
> project warp:
> Unable to checkout from SCM
> [ERROR] Provider message:
> [ERROR] The git-clone command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'C\Users\daspilker\workspaces\myproject' does not appear to be
> a git repository
> [ERROR] fatal: The remote end hung up unexpectedly
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :myproject
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira