[ http://jira.codehaus.org/browse/CONTINUUM-529?page=comments#action_75068 ] Trygve Laugstol commented on CONTINUUM-529: -------------------------------------------
I'm not sure how to solve this because this means that Maven will construct a different SCM URL given the child POM and a repository than Continuum will. An alternative is to include the artifact and group id in the <module> section to make it possible to correctly map the path and the artifact. > Modules (child) scm connection URLs are not constructed correctly > ----------------------------------------------------------------- > > Key: CONTINUUM-529 > URL: http://jira.codehaus.org/browse/CONTINUUM-529 > Project: Continuum > Issue Type: Bug > Components: Core system, SCM > Affects Versions: 1.0.2 > Reporter: Grégory Joseph > Priority: Critical > Fix For: 1.1 > > > It *seems* to me that, when adding a parent pom to continuum, which has > <modules> defined, but the scm url only defined in the parent, it gets and > parses the child poms correctly, but their scm URLs are build as > ${parentScmUrl}/${childArtifactId} , while I think they should rather be > ${parentScmUrl}/${modulePath} > Maybe this is a maven inheritance issue, though ? -- 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
