[ https://issues.apache.org/jira/browse/SCM-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964733#comment-17964733 ]
Olivier Lamy commented on SCM-570: ---------------------------------- This project has moved from Jira to GitHub Issues. This issue was migrated to [apache/maven-scm#784|https://github.com/apache/maven-scm/issues/784]. > SCM connection URL is inherited with artifactId added > ----------------------------------------------------- > > Key: SCM-570 > URL: https://issues.apache.org/jira/browse/SCM-570 > Project: Maven SCM (Moved to GitHub Issues) > Issue Type: Bug > Components: maven-plugin > Reporter: Dmitry Murashenkov > Assignee: Benjamin Bentmann > Priority: Major > > Not sure if this is a bug or a feature (could not find documentation) and if > it applies to scm plugin or maven core. > TC: > 1. Make a parent pom: > <scm> > <connection>${svn.repository}/trunk/${component.folder}</connection> > </scm> > <properties> > <svn.repository>scm:svn:svn://localhost/myRepo</svn.repository> > <component.folder>components/myParentPomComponent</component.folder> > </properties> > 2. Make child pom: > <parent> > <artifactId>myParentPomComponent</artifactId> > </parent> > <properties> > <component.folder>components/myChildComponent</component.folder> > </properties> > 3. In folder with child component perform > mvn help:effective-pom|grep svn > Expected result: > scm:svn:svn://localhost/myRepo/trunk/components/myChildComponent > Actual result: > scm:svn:svn://localhost/myRepo/trunk/components/myChildComponent/myChildComponent > 4. Add to child pom: > <scm> > <connection>${svn.repository}/trunk/${component.folder}</connection> > </scm> > 5. In folder with child component perform > mvn help:effective-pom|grep svn > Actual result: > scm:svn:svn://localhost/myRepo/trunk/components/myChildComponent > ---------------------- > So if <scm> is omited it is inherited with artifactId applied and that breaks > the schema when you specify folder with this component in a property. -- This message was sent by Atlassian Jira (v8.20.10#820010)