[
http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115385
]
Richard van der Hoff commented on MNG-2915:
-------------------------------------------
We actually found a workaround for this problem in our particular usecase.
The main distributionManagement section in our parent-pom has the url ready to
be appended to by child poms, and the parent-pom also has a profile which
overrides it just for that one pom; thus:
{code:xml}
<profiles>
<profile>
<id>deploying-base-pom-itself</id>
<activation>
<file>
<exists>THIS-IS-base-pom</exists>
</file>
</activation>
<distributionManagement>
<site>
<id>mx-release</id>
<url>scpexe://host/blah/base-pom</url>
</site>
</distributionManagement>
</profile>
</profiles>
{code}
This profile is then enabled for the base pom by creating a file entitled
THIS-IS-base-pom.
I think this might also work for the scm url.
Obviously this becomes a less useful solution for deeper project heirarchies,
but it works pretty well for us.
> 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
