[MNG-4763] SCM entry is determined wrongly when aggregating project is not a parent

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 2.2.1
• Component/s: Plugin API
• Environment: Windows XP
• Assignee: Benjamin Bentmann
• Reporter: Mateusz Prokopowicz
• Created: 13/Aug/10 03:54
• Updated: 13/Aug/10 04:16
• Resolved: 13/Aug/10 04:14

Description

Hello,
I'm writing a plugin to check if SCM entry matches the real svn path. The scm entry is got from ${project.scm} parameter, to get a real path I'm incorporating svnKit library. If the aggregated project doesn't have its own scm tag, it iherites one from parent with appended artifact id. However, according with the project layout the scm should be got from the aggregator. The issue is presented on the following example

aggregator pom:

<project>    
    <artifactId>aggregator</artifactId>
    <scm><connection>scm:svn:http://host.com/svn/aggregator/trunk</connection></scm>
    <modules><module>child</module></modules>
<project>

parent pom:

<project>
    <artifactId>parent</artifactId>
    <scm><connection>scm:svn:http://host.com/svn/parent/trunk</connection></scm>
<project>

child pom

<project>
    <parent><artifactId>parent</artifactId></parent>
    <artifactId>child</artifactId>   
<project>

The scm entry connection (${project.scm}.connection) for child is scm:svn:http://host.com/svn/parent/trunk/child but shoud be scm:svn:http://host.com/svn/aggregator/trunk/child

Issue Links

• is related to: MNG-2006 Module SCM URL is resolved as [...]/parent/module regardless of relativePath