[MNG-4878] Inheritance of URLs behaves differently for aggregated and non-aggregated child projects

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 3.0
• Component/s: Inheritance and Interpolation
• Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200); Java version: 1.6.0_20
• Assignee: Benjamin Bentmann
• Reporter: Andreas Sewe
• Created: 25/Oct/10 11:20
• Updated: 25/Jan/11 06:02
• Resolved: 30/Oct/10 09:28

Description

AFAIK, inheritance and aggregation are orthogonal in Maven. Whether a child project is a module of its parent, however, affects how URLs are inherited. (This bug affects /project/url, /project/distributionManagement/site/url, /project/scm/connection, /project/scm/developerConnection, and /project/scm/url.)

This is exemplified by the attached projects, which serve as a testcase. The aggregated child project does respect the trailing slash of its parent's URLs and thus does not append its own artifactId to the URLs. The non-aggregated child, however, does not respect the trailing slash; consequently, its artifactId is added erroneously: A /project/url of http://www.example.org/projects/${project.artifactId}/ is turned into http://www.example.org/projects/non-aggregated-child/non-aggregated-child/ in the non-aggregated child project, whereas it becomes http://www.example.org/projects/aggregated-child/ in the aggregated child project. (Note that both projects are children of the same parent project.)

Issue Links

• duplicates: MNG-4508 No way to avoid adding artifactId to site urls
• is duplicated by: MNG-4994 [regression] Inheritance of project/site/scm URLs does not take child's relative location to parent into account
• is related to: MNG-2006 Module SCM URL is resolved as [...]/parent/module regardless of relativePath
• is related to: MNG-3244 inherited site url not properly handling parameters