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:36:05 UTC
[jira] Commented: (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:comment-tabpanel&focusedCommentId=241522#action_241522 ]
Andreas Sewe commented on MNG-4878:
-----------------------------------
Fair enough; I'm not to keen on the "append artifactId to URL" feature myself. I just hope that this is not a deeper issue with the way inheritance and aggregation are implemented, so that this issue doesn't pop up at other places as well.
> 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