[
http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115366
]
Cyril ADRIAN commented on MNG-2915:
-----------------------------------
Hello,
I have the same problem with scm URLs which have the artifactId appended too.
That's extremely disturbing because we don't want to nest projects with an scm
repository (FWIW it's svn). We prefer a flat structure even if we have
parent-child dependancies.
I think the priority of this bug should be more important.
Is there a way we can help with the issue?
Thanks
> 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: 2.1
>
>
> 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
