Continuum

Modules (child) scm connection URLs are not constructed correctly

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0.2
  • Fix Version/s: 1.1-alpha-1
  • Component/s: Core system, SCM
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

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 ?

Issue Links

Activity

Hide
Martin van den Bemt added a comment -

You will run into other problems when the scm url is inherited and the location in scm != artifactId, so better define the correct scm url in the child pom. So if you want this fix, this defintely isn't a bug, but at most an enhancement or request for this kind of functionality.

Show
Martin van den Bemt added a comment - You will run into other problems when the scm url is inherited and the location in scm != artifactId, so better define the correct scm url in the child pom. So if you want this fix, this defintely isn't a bug, but at most an enhancement or request for this kind of functionality.
Hide
Joakim Erdfelt added a comment -

This problem can be reproduced with the plexus-security components.

https://svn.codehaus.org/plexus/trunk/plexus-sandbox/plexus-components/plexus-security/

Show
Joakim Erdfelt added a comment - This problem can be reproduced with the plexus-security components. https://svn.codehaus.org/plexus/trunk/plexus-sandbox/plexus-components/plexus-security/
Hide
Trygve Laugstol added a comment -

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.

Show
Trygve Laugstol added a comment - 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.
Hide
Trygve Laugstol added a comment -

Setting the priority level back to normal.

Show
Trygve Laugstol added a comment - Setting the priority level back to normal.
Hide
Emmanuel Venisse added a comment -

Fixed.

Show
Emmanuel Venisse added a comment - Fixed.

People

Vote (12)
Watch (9)

Dates

  • Created:
    Updated:
    Resolved: