maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Graham (JIRA)" <j...@codehaus.org>
Subject [jira] (SCM-656) Building maven-scm-1.6 requires a native install of git.
Date Sat, 04 Feb 2012 01:49:03 GMT

    [ https://jira.codehaus.org/browse/SCM-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290748#comment-290748
] 

Chris Graham edited comment on SCM-656 at 2/3/12 7:48 PM:
----------------------------------------------------------

Opps. I'm not sure if this will work:

        if ( !isSystemCmd( GitScmTestUtils.GIT_COMMAND_LINE ) )
        {
            System.err.println( "'" + GitScmTestUtils.GIT_COMMAND_LINE + "' is not a system
command. Ignored "
                + getName() + "." );
            return;
        }

because on my system, I have git.cmd in the path, not git.exe.

So it incorrectly thinks that git is not available. (When it is).

When I've added the git bin dir into the path (where git.exe lives), the test successfully
runs - it does not erroneously skip the test.

                
      was (Author: chrisgwarp):
    Opps. I'm not sure if this will work:

                  
> Building maven-scm-1.6 requires a native install of git.
> --------------------------------------------------------
>
>                 Key: SCM-656
>                 URL: https://jira.codehaus.org/browse/SCM-656
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-git
>    Affects Versions: 1.6
>         Environment: Windows XP
> maven 2.2.1
>            Reporter: Chris Graham
>            Assignee: Olivier Lamy
>             Fix For: 1.7
>
>         Attachments: git-no-exe.patch, git-test-fail.patch
>
>
> Check out a fresh copy of maven-scm-1.6 and attempt to build via "mvn clean install"
and it fails due to a missing native git.exe not being present.
> Running org.apache.maven.scm.provider.git.gitexe.command.checkout.GitExeCheckOutCommandNoBranchTest
> [INFO] Executing: cmd.exe /X /C "git clone C\Workspaces\\maven-scm-1.6\maven-scm-providers\maven-scm-providers-git\maven-scm-provider-gitexe\src\test\resources\repository_no_branch
C:\Workspaces\maven-scm-1.6\maven-scm-providers\maven-scm-providers-git\maven-scm-provider-gitexe\target\checkin-nobranch"
> [INFO] Working directory: C:\Workspaces\maven-scm-1.6\maven-scm-providers\maven-scm-providers-git\maven-scm-provider-gitexe\target
> ----------------------------------------------------------------------
> Provider message
> ----------------------------------------------------------------------
> The git-clone command failed.
> ----------------------------------------------------------------------
> ----------------------------------------------------------------------
> Command output
> ----------------------------------------------------------------------
> 'git' is not recognized as an internal or external command,
> operable program or batch file.
> ----------------------------------------------------------------------
> [INFO] Executing: cmd.exe /X /C "git clone C\Workspaces\maven-scm-1.6\maven-scm-providers\maven-scm-providers-git\maven-scm-provider-gitexe\src\test\resources\repository_no_branch
C:\Workspaces\maven-scm-1.6\maven-scm-providers\maven-scm-providers-git\maven-scm-provider-gitexe\target\checkin-nobranch"
> [INFO] Working directory: C:\Workspaces\maven-scm-1.6\maven-scm-providers\maven-scm-providers-git\maven-scm-provider-gitexe\target
> ----------------------------------------------------------------------
> Provider message
> ----------------------------------------------------------------------
> The git-clone command failed.
> ----------------------------------------------------------------------
> ----------------------------------------------------------------------
> Command output
> ----------------------------------------------------------------------
> 'git' is not recognized as an internal or external command,
> operable program or batch file.

--
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

        

Mime
View raw message