[
http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174940#action_174940
]
Paul Harrison commented on MNG-2915:
------------------------------------
I would like to add a plea for this behaviour to be modified - we too have a
similar 3 level pom inheritance hierarchy, and it is irritating to have to
specify the URLs in the final level when the root is specified in the top level
because the intermedate level is automactically inserted. I think that the
problems come about here because there is not a clear distinction made between
pom inhertance and project aggregation - typically if a project only inherits
from another project then the values should only be inherited, without
modification - it a project is an aggregated child as well, then various URLs
can have artifactIds automatically added to the end.
Even with this modification to behaviour I would also support the suggestion
above that automatic appending of artifactId only occurs when the URL ends
explictly with a "/" - this allows for more complex URL layouts to be specified
in the root POM with the use of variables such as the
<url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
which I think is a rather commonly desired layout.
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MNG-2915
> URL: http://jira.codehaus.org/browse/MNG-2915
> Project: Maven 2
> Issue Type: Improvement
> Components: Sites & Reporting
> Affects Versions: 2.0.5
> Reporter: Richard van der Hoff
> Priority: Minor
> Fix For: 3.x
>
>
> Currently, whenever a child pom inherits from a parent (and doesn't override
> the relevant settings), both project.url and
> project.distributionManagement.site.url have the name of the child artifact
> appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects,
> with useful settings such as distributionManagement, and I'd like to be able
> to deploy their sites to a single directory and have Apache generate me a
> directory listing for all the child projects. However, I curently have no way
> of releasing the parent project without obliterating the list of child
> projects.
--
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
