You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Petter Måhlén (JIRA)" <ji...@codehaus.org> on 2009/03/05 16:26:13 UTC
[jira] Created: (SCM-442) Incorrect SCM URL constructed when using
parent POM that is not in the parent directory
Incorrect SCM URL constructed when using parent POM that is not in the parent directory
---------------------------------------------------------------------------------------
Key: SCM-442
URL: http://jira.codehaus.org/browse/SCM-442
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-git
Affects Versions: 1.1
Reporter: Petter Måhlén
We have a parent corporate POM that is not in the parent folder of each project. When running release:perform, the correct (as specified) GIT SCM URL is not used, but instead a URL is created by appending the Maven artifact name to the SCM URL of the parent corporate POM project. Which doesn't make sense at all to me:
1. There is no requirement (and in fact bad practice in a lot of cases) that the POM hierarchy should map exactly to the folder hierarchy. So a parent POM doesn't have to reside in a parent directory.
2. There is no requirement (but maybe good practice) to have folder names in SCM be the same as the artifact names. In our case, we have a bad artifact name that we want to keep so as not to have to modify a lot of POMs, but we wanted a clearer repository name for the new Git repository.
This is the error message from the 'mvn release:perform' command.
INFO] Executing: /bin/sh -c cd /Users/pettermahlen/git/sponsoredlinks-client/target && git clone git://git.shopzilla.com/java/common.mvn.git/slg_client /Users/pettermahlen/git/sponsoredlinks-client/target/checkout
[INFO] Working directory: /Users/pettermahlen/git/sponsoredlinks-client/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: The remote end hung up unexpectedly
The SCM configuration from the 'slg_client' pom.xml is;
<scm>
<connection>scm:git:git://git.shopzilla.com/site/client/sponsoredlinks-client</connection>
</scm>
The workaround that I have found is to manually edit the release.properties file and change to using the correct SCM URL.
--
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
[jira] Updated: (SCM-442) Incorrect SCM URL constructed when using
parent POM that is not in the parent directory
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy updated SCM-442:
-----------------------------
Assignee: Olivier Lamy
Fix Version/s: 1.2
> Incorrect SCM URL constructed when using parent POM that is not in the parent directory
> ---------------------------------------------------------------------------------------
>
> Key: SCM-442
> URL: http://jira.codehaus.org/browse/SCM-442
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.1
> Reporter: Petter Måhlén
> Assignee: Olivier Lamy
> Fix For: 1.2
>
>
> We have a parent corporate POM that is not in the parent folder of each project. When running release:perform, the correct (as specified) GIT SCM URL is not used, but instead a URL is created by appending the Maven artifact name to the SCM URL of the parent corporate POM project. Which doesn't make sense at all to me:
> 1. There is no requirement (and in fact bad practice in a lot of cases) that the POM hierarchy should map exactly to the folder hierarchy. So a parent POM doesn't have to reside in a parent directory.
> 2. There is no requirement (but maybe good practice) to have folder names in SCM be the same as the artifact names. In our case, we have a bad artifact name that we want to keep so as not to have to modify a lot of POMs, but we wanted a clearer repository name for the new Git repository.
> This is the error message from the 'mvn release:perform' command.
> INFO] Executing: /bin/sh -c cd /Users/pettermahlen/git/sponsoredlinks-client/target && git clone git://git.shopzilla.com/java/common.mvn.git/slg_client /Users/pettermahlen/git/sponsoredlinks-client/target/checkout
> [INFO] Working directory: /Users/pettermahlen/git/sponsoredlinks-client/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: The remote end hung up unexpectedly
> The SCM configuration from the 'slg_client' pom.xml is;
> <scm>
> <connection>scm:git:git://git.shopzilla.com/site/client/sponsoredlinks-client</connection>
> </scm>
> The workaround that I have found is to manually edit the release.properties file and change to using the correct SCM URL.
--
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
[jira] Updated: (SCM-442) Incorrect SCM URL constructed when using
parent POM that is not in the parent directory
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy updated SCM-442:
-----------------------------
Assignee: (was: Olivier Lamy)
Fix Version/s: (was: 1.2)
1.3
> Incorrect SCM URL constructed when using parent POM that is not in the parent directory
> ---------------------------------------------------------------------------------------
>
> Key: SCM-442
> URL: http://jira.codehaus.org/browse/SCM-442
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.1
> Reporter: Petter Måhlén
> Fix For: 1.3
>
>
> We have a parent corporate POM that is not in the parent folder of each project. When running release:perform, the correct (as specified) GIT SCM URL is not used, but instead a URL is created by appending the Maven artifact name to the SCM URL of the parent corporate POM project. Which doesn't make sense at all to me:
> 1. There is no requirement (and in fact bad practice in a lot of cases) that the POM hierarchy should map exactly to the folder hierarchy. So a parent POM doesn't have to reside in a parent directory.
> 2. There is no requirement (but maybe good practice) to have folder names in SCM be the same as the artifact names. In our case, we have a bad artifact name that we want to keep so as not to have to modify a lot of POMs, but we wanted a clearer repository name for the new Git repository.
> This is the error message from the 'mvn release:perform' command.
> INFO] Executing: /bin/sh -c cd /Users/pettermahlen/git/sponsoredlinks-client/target && git clone git://git.shopzilla.com/java/common.mvn.git/slg_client /Users/pettermahlen/git/sponsoredlinks-client/target/checkout
> [INFO] Working directory: /Users/pettermahlen/git/sponsoredlinks-client/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: The remote end hung up unexpectedly
> The SCM configuration from the 'slg_client' pom.xml is;
> <scm>
> <connection>scm:git:git://git.shopzilla.com/site/client/sponsoredlinks-client</connection>
> </scm>
> The workaround that I have found is to manually edit the release.properties file and change to using the correct SCM URL.
--
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
[jira] Commented: (SCM-442) Incorrect SCM URL constructed when
using parent POM that is not in the parent directory
Posted by "Petter Måhlén (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174758#action_174758 ]
Petter Måhlén commented on SCM-442:
-----------------------------------
Apologies if I sounded aggressive in my question, I didn't mean to. I just wanted to understand the 'wontfix' status, whether that meant that it was already fixed or a user error, just to know if it would bite us again or not, so I can update our internal recommendations.
I haven't been able to test this further because I haven't been in the position of releasing anything where it happens lately, hence the lack of answers to previous comments. Unfortunately, with a launch looming large in the near future, I won't be able to find the time to do any testing/investigations of this for a while. :(
> Incorrect SCM URL constructed when using parent POM that is not in the parent directory
> ---------------------------------------------------------------------------------------
>
> Key: SCM-442
> URL: http://jira.codehaus.org/browse/SCM-442
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.1
> Reporter: Petter Måhlén
> Assignee: Olivier Lamy
>
> We have a parent corporate POM that is not in the parent folder of each project. When running release:perform, the correct (as specified) GIT SCM URL is not used, but instead a URL is created by appending the Maven artifact name to the SCM URL of the parent corporate POM project. Which doesn't make sense at all to me:
> 1. There is no requirement (and in fact bad practice in a lot of cases) that the POM hierarchy should map exactly to the folder hierarchy. So a parent POM doesn't have to reside in a parent directory.
> 2. There is no requirement (but maybe good practice) to have folder names in SCM be the same as the artifact names. In our case, we have a bad artifact name that we want to keep so as not to have to modify a lot of POMs, but we wanted a clearer repository name for the new Git repository.
> This is the error message from the 'mvn release:perform' command.
> INFO] Executing: /bin/sh -c cd /Users/pettermahlen/git/sponsoredlinks-client/target && git clone git://git.shopzilla.com/java/common.mvn.git/slg_client /Users/pettermahlen/git/sponsoredlinks-client/target/checkout
> [INFO] Working directory: /Users/pettermahlen/git/sponsoredlinks-client/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: The remote end hung up unexpectedly
> The SCM configuration from the 'slg_client' pom.xml is;
> <scm>
> <connection>scm:git:git://git.shopzilla.com/site/client/sponsoredlinks-client</connection>
> </scm>
> The workaround that I have found is to manually edit the release.properties file and change to using the correct SCM URL.
--
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
[jira] Commented: (SCM-442) Incorrect SCM URL constructed when
using parent POM that is not in the parent directory
Posted by "Mark Struberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174747#action_174747 ]
Mark Struberg commented on SCM-442:
-----------------------------------
Hi Petter!
I think the reason why Olivier did set it to wontfix is because this looks pretty similar to a known release 'issue', which has a known workaround and you didn't respond to my questions for 3 weeks. So he probably assumed you fixed it already.
>From my side I can only say that the maven-scm-providers-git seems to correctly executes the commands the release-plugin/release-manager tells him to do. So this is most probably not a maven-scm bug. Maybe it is one in the release-plugin, but first search for 'flat structure'
I'm not sure whats the status of SCM-392 , SCM-342 and MRELEASE-362 though.
> Incorrect SCM URL constructed when using parent POM that is not in the parent directory
> ---------------------------------------------------------------------------------------
>
> Key: SCM-442
> URL: http://jira.codehaus.org/browse/SCM-442
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.1
> Reporter: Petter Måhlén
> Assignee: Olivier Lamy
>
> We have a parent corporate POM that is not in the parent folder of each project. When running release:perform, the correct (as specified) GIT SCM URL is not used, but instead a URL is created by appending the Maven artifact name to the SCM URL of the parent corporate POM project. Which doesn't make sense at all to me:
> 1. There is no requirement (and in fact bad practice in a lot of cases) that the POM hierarchy should map exactly to the folder hierarchy. So a parent POM doesn't have to reside in a parent directory.
> 2. There is no requirement (but maybe good practice) to have folder names in SCM be the same as the artifact names. In our case, we have a bad artifact name that we want to keep so as not to have to modify a lot of POMs, but we wanted a clearer repository name for the new Git repository.
> This is the error message from the 'mvn release:perform' command.
> INFO] Executing: /bin/sh -c cd /Users/pettermahlen/git/sponsoredlinks-client/target && git clone git://git.shopzilla.com/java/common.mvn.git/slg_client /Users/pettermahlen/git/sponsoredlinks-client/target/checkout
> [INFO] Working directory: /Users/pettermahlen/git/sponsoredlinks-client/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: The remote end hung up unexpectedly
> The SCM configuration from the 'slg_client' pom.xml is;
> <scm>
> <connection>scm:git:git://git.shopzilla.com/site/client/sponsoredlinks-client</connection>
> </scm>
> The workaround that I have found is to manually edit the release.properties file and change to using the correct SCM URL.
--
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
[jira] Closed: (SCM-442) Incorrect SCM URL constructed when using
parent POM that is not in the parent directory
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy closed SCM-442.
----------------------------
Assignee: Olivier Lamy
Resolution: Won't Fix
Fix Version/s: (was: 1.3)
> Incorrect SCM URL constructed when using parent POM that is not in the parent directory
> ---------------------------------------------------------------------------------------
>
> Key: SCM-442
> URL: http://jira.codehaus.org/browse/SCM-442
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.1
> Reporter: Petter Måhlén
> Assignee: Olivier Lamy
>
> We have a parent corporate POM that is not in the parent folder of each project. When running release:perform, the correct (as specified) GIT SCM URL is not used, but instead a URL is created by appending the Maven artifact name to the SCM URL of the parent corporate POM project. Which doesn't make sense at all to me:
> 1. There is no requirement (and in fact bad practice in a lot of cases) that the POM hierarchy should map exactly to the folder hierarchy. So a parent POM doesn't have to reside in a parent directory.
> 2. There is no requirement (but maybe good practice) to have folder names in SCM be the same as the artifact names. In our case, we have a bad artifact name that we want to keep so as not to have to modify a lot of POMs, but we wanted a clearer repository name for the new Git repository.
> This is the error message from the 'mvn release:perform' command.
> INFO] Executing: /bin/sh -c cd /Users/pettermahlen/git/sponsoredlinks-client/target && git clone git://git.shopzilla.com/java/common.mvn.git/slg_client /Users/pettermahlen/git/sponsoredlinks-client/target/checkout
> [INFO] Working directory: /Users/pettermahlen/git/sponsoredlinks-client/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: The remote end hung up unexpectedly
> The SCM configuration from the 'slg_client' pom.xml is;
> <scm>
> <connection>scm:git:git://git.shopzilla.com/site/client/sponsoredlinks-client</connection>
> </scm>
> The workaround that I have found is to manually edit the release.properties file and change to using the correct SCM URL.
--
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
[jira] Commented: (SCM-442) Incorrect SCM URL constructed when
using parent POM that is not in the parent directory
Posted by "Petter Måhlén (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174744#action_174744 ]
Petter Måhlén commented on SCM-442:
-----------------------------------
I don't understand the 'WONTFIX' status? Does your comment mean this is no longer reproducible? It is (was) obviously a bug, since the child project got the completely wrong URL when trying to check out things from Git. See the URL in the 'git clone' command in the bug report that has '.../java/common.mvn.git/slg_client' at the end, whereas the correct URL that was specified in the child POM is '.../site/client/sponsoredlinks-client'. The first URL was the parent POM's Git URL + the name of the Maven artifact created in the child project.
> Incorrect SCM URL constructed when using parent POM that is not in the parent directory
> ---------------------------------------------------------------------------------------
>
> Key: SCM-442
> URL: http://jira.codehaus.org/browse/SCM-442
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.1
> Reporter: Petter Måhlén
> Assignee: Olivier Lamy
>
> We have a parent corporate POM that is not in the parent folder of each project. When running release:perform, the correct (as specified) GIT SCM URL is not used, but instead a URL is created by appending the Maven artifact name to the SCM URL of the parent corporate POM project. Which doesn't make sense at all to me:
> 1. There is no requirement (and in fact bad practice in a lot of cases) that the POM hierarchy should map exactly to the folder hierarchy. So a parent POM doesn't have to reside in a parent directory.
> 2. There is no requirement (but maybe good practice) to have folder names in SCM be the same as the artifact names. In our case, we have a bad artifact name that we want to keep so as not to have to modify a lot of POMs, but we wanted a clearer repository name for the new Git repository.
> This is the error message from the 'mvn release:perform' command.
> INFO] Executing: /bin/sh -c cd /Users/pettermahlen/git/sponsoredlinks-client/target && git clone git://git.shopzilla.com/java/common.mvn.git/slg_client /Users/pettermahlen/git/sponsoredlinks-client/target/checkout
> [INFO] Working directory: /Users/pettermahlen/git/sponsoredlinks-client/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: The remote end hung up unexpectedly
> The SCM configuration from the 'slg_client' pom.xml is;
> <scm>
> <connection>scm:git:git://git.shopzilla.com/site/client/sponsoredlinks-client</connection>
> </scm>
> The workaround that I have found is to manually edit the release.properties file and change to using the correct SCM URL.
--
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
[jira] Commented: (SCM-442) Incorrect SCM URL constructed when
using parent POM that is not in the parent directory
Posted by "Mark Struberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170171#action_170171 ]
Mark Struberg commented on SCM-442:
-----------------------------------
the SCM URL creation is usually not part of the scm-provider but done by the release-plugin. So this is most probably a release bug
> Incorrect SCM URL constructed when using parent POM that is not in the parent directory
> ---------------------------------------------------------------------------------------
>
> Key: SCM-442
> URL: http://jira.codehaus.org/browse/SCM-442
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.1
> Reporter: Petter Måhlén
> Assignee: Olivier Lamy
> Fix For: 1.2
>
>
> We have a parent corporate POM that is not in the parent folder of each project. When running release:perform, the correct (as specified) GIT SCM URL is not used, but instead a URL is created by appending the Maven artifact name to the SCM URL of the parent corporate POM project. Which doesn't make sense at all to me:
> 1. There is no requirement (and in fact bad practice in a lot of cases) that the POM hierarchy should map exactly to the folder hierarchy. So a parent POM doesn't have to reside in a parent directory.
> 2. There is no requirement (but maybe good practice) to have folder names in SCM be the same as the artifact names. In our case, we have a bad artifact name that we want to keep so as not to have to modify a lot of POMs, but we wanted a clearer repository name for the new Git repository.
> This is the error message from the 'mvn release:perform' command.
> INFO] Executing: /bin/sh -c cd /Users/pettermahlen/git/sponsoredlinks-client/target && git clone git://git.shopzilla.com/java/common.mvn.git/slg_client /Users/pettermahlen/git/sponsoredlinks-client/target/checkout
> [INFO] Working directory: /Users/pettermahlen/git/sponsoredlinks-client/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: The remote end hung up unexpectedly
> The SCM configuration from the 'slg_client' pom.xml is;
> <scm>
> <connection>scm:git:git://git.shopzilla.com/site/client/sponsoredlinks-client</connection>
> </scm>
> The workaround that I have found is to manually edit the release.properties file and change to using the correct SCM URL.
--
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
[jira] Commented: (SCM-442) Incorrect SCM URL constructed when
using parent POM that is not in the parent directory
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174675#action_174675 ]
Olivier Lamy commented on SCM-442:
----------------------------------
you can certainly add a scm element in the pom
> Incorrect SCM URL constructed when using parent POM that is not in the parent directory
> ---------------------------------------------------------------------------------------
>
> Key: SCM-442
> URL: http://jira.codehaus.org/browse/SCM-442
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.1
> Reporter: Petter Måhlén
>
> We have a parent corporate POM that is not in the parent folder of each project. When running release:perform, the correct (as specified) GIT SCM URL is not used, but instead a URL is created by appending the Maven artifact name to the SCM URL of the parent corporate POM project. Which doesn't make sense at all to me:
> 1. There is no requirement (and in fact bad practice in a lot of cases) that the POM hierarchy should map exactly to the folder hierarchy. So a parent POM doesn't have to reside in a parent directory.
> 2. There is no requirement (but maybe good practice) to have folder names in SCM be the same as the artifact names. In our case, we have a bad artifact name that we want to keep so as not to have to modify a lot of POMs, but we wanted a clearer repository name for the new Git repository.
> This is the error message from the 'mvn release:perform' command.
> INFO] Executing: /bin/sh -c cd /Users/pettermahlen/git/sponsoredlinks-client/target && git clone git://git.shopzilla.com/java/common.mvn.git/slg_client /Users/pettermahlen/git/sponsoredlinks-client/target/checkout
> [INFO] Working directory: /Users/pettermahlen/git/sponsoredlinks-client/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: The remote end hung up unexpectedly
> The SCM configuration from the 'slg_client' pom.xml is;
> <scm>
> <connection>scm:git:git://git.shopzilla.com/site/client/sponsoredlinks-client</connection>
> </scm>
> The workaround that I have found is to manually edit the release.properties file and change to using the correct SCM URL.
--
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