[
https://jira.codehaus.org/browse/MNG-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315317#comment-315317
]
Darryl L. Miles commented on MNG-4508:
--------------------------------------
Remove the inheritance rules but provide a maven configured variable
${maven.project.path} or something that will becomes "/parent-parent/parent" in
deepest level of a 3 level project. The super POM will be an empty string.
The mid-level will be "/parent-parent". Now users get the best of both worlds
without being chained to the convention.
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MNG-4508
> URL: https://jira.codehaus.org/browse/MNG-4508
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Inheritance and Interpolation
> Reporter: Richard van der Hoff
> Priority: Minor
> Fix For: 3.2
>
>
> 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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
