maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <>
Subject [jira] Commented: (SCM-442) Incorrect SCM URL constructed when using parent POM that is not in the parent directory
Date Thu, 30 Apr 2009 07:26:45 GMT


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:
>             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:// /Users/pettermahlen/git/sponsoredlinks-client/target/checkout
> [INFO] Working directory: /Users/pettermahlen/git/sponsoredlinks-client/target
> [ERROR] The git-clone command failed.
> [INFO] ------------------------------------------------------------------------
> [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://</connection>
>   </scm>
> The workaround that I have found is to manually edit the 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:
For more information on JIRA, see:


View raw message