maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Paramonov (JIRA)" <j...@codehaus.org>
Subject [jira] Reopened: (MRELEASE-590) release:perform fails on Git repository relative path
Date Sat, 21 Aug 2010 23:45:35 GMT

     [ http://jira.codehaus.org/browse/MRELEASE-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrey Paramonov reopened MRELEASE-590:
---------------------------------------


According to the error message, the failed operation was clone, and cloning from present directory
makes perfect sense in Git, and it actually works well in this plugin when you specify absolute
path to the present directory.

According to SCM-444 the present directory syntax also make sense for other Git/Maven users.

Can you please explain what you mean by Git provider? As I noted before the following command
works fine in Git itself:

git clone file://. target/checkout

and SCM plugin was also updated to support relative paths. Plus, since release:prepare works
as expected, your Git provider definitely supports relative paths in check in operation. If
it doesn't support them in check out, then it's a bug.

> release:perform fails on Git repository relative path
> -----------------------------------------------------
>
>                 Key: MRELEASE-590
>                 URL: http://jira.codehaus.org/browse/MRELEASE-590
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: perform
>    Affects Versions: 2.0
>         Environment: MacOS X 10.6.4, Maven 2.1.0
>            Reporter: Andrey Paramonov
>            Assignee: Mark Struberg
>         Attachments: pom.xml
>
>
> Running release:perform on relative Git path
> {code}
> <scm>
>     <connection>scm:git:file://.</connection>
>     <developerConnection>scm:git:file://.</developerConnection>
>     <url>scm:git:file://.</url>
> </scm>
> {code}
> fails with the error
> {code}
> [INFO] [release:perform]
> [INFO] Checking out the project to perform the release ...
> [INFO] Executing: /bin/sh -c cd /Users/andrey/projects/demos/gitmaven/target &&
git clone file://. /Users/andrey/projects/demos/gitmaven/target/checkout
> [INFO] Working directory: /Users/andrey/projects/demos/gitmaven/target
> [ERROR] The git-clone command failed.
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Unable to checkout from SCM
> Provider message:
> The git-clone command failed.
> Command output:
> fatal: '.' does not appear to be a git repository
> fatal: The remote end hung up unexpectedly
> {code}
> It works fine for absolute path though.
> Also to note, when I run the same clone command in the shell, it works without any problem
> {code}
> $ git clone file://. /Users/andrey/projects/demos/gitmaven/target/checkout
> Initialized empty Git repository in /Users/andrey/projects/demos/gitmaven/target/checkout/.git/
> remote: Counting objects: 100, done.
> remote: Compressing objects: 100% (89/89), done.
> remote: Total 100 (delta 38), reused 0 (delta 0)
> Receiving objects: 100% (100/100), 9.52 KiB, done.
> Resolving deltas: 100% (38/38), done.
> {code}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message