Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
None
-
None
-
None
Description
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.
Attachments
Issue Links
- duplicates
-
MNG-2219 artifactId appended to URL in scm reports. Problem apparently comes from the core.
- Closed