You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andreas Sewe (JIRA)" <ji...@codehaus.org> on 2010/10/30 16:19:06 UTC

[jira] Reopened: (MNG-4878) Inheritance of URLs behaves differently for aggregated and non-aggregated child projects

     [ http://jira.codehaus.org/browse/MNG-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Sewe reopened MNG-4878:
-------------------------------


I'm sorry, but I disagree with the assessment that this issue is a duplicate of MNG-4508. It's not really about being able to suppress the addition of the artifactId to URLs; rather, it's about a case (which just happens to involve URLs) where the use of *aggregation* changes the way *inheritance* works. As far as I understand it (see, e.g., the POM reference at http://maven.apache.org/pom.html#Inheritance_v) inheritance and aggregation are meant to be _orthogonal_ language features; using one shouldn't change the behaviour of the other.

> Inheritance of URLs behaves differently for aggregated and non-aggregated child projects
> ----------------------------------------------------------------------------------------
>
>                 Key: MNG-4878
>                 URL: http://jira.codehaus.org/browse/MNG-4878
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Inheritance and Interpolation
>    Affects Versions: 3.0
>         Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200)
> Java version: 1.6.0_20
>            Reporter: Andreas Sewe
>            Assignee: Benjamin Bentmann
>         Attachments: testcase-project.tar.gz
>
>
> 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.)

-- 
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