SCM entry is determined wrongly when aggregating project is not a parent
------------------------------------------------------------------------
Key: MNG-4763
URL: http://jira.codehaus.org/browse/MNG-4763
Project: Maven 2 & 3
Issue Type: Bug
Components: Plugin API
Affects Versions: 2.2.1
Environment: Windows XP
Reporter: Mateusz Prokopowicz
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:
{code:xml}
<project>
<artifactId>aggregator</artifactId>
<scm><connection>scm:svn:http://host.com/svn/aggregator/trunk</connection></scm>
<modules><module>child</module></modules>
<project>
{code}
parent pom:
{code:xml}
<project>
<artifactId>parent</artifactId>
<scm><connection>scm:svn:http://host.com/svn/parent/trunk</connection></scm>
<project>
{code}
child pom
{code:xml}
<project>
<parent><artifactId>parent</artifactId></parent>
<artifactId>child</artifactId>
<project>
{code}
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
--
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
