[
http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115388
]
cadrian edited comment on MNG-2915 at 11/29/07 10:40 AM:
--------------------------------------------------------------
Good idea, thanks :-)
Although I still need a proper fix because we usually have two levels:
- our "enterprise" pom
- an "application head" containing all the modules an dinheritting from the
"enterprise" pom
- the application modules inheritting from the "application head"
Anyway, thanks for the idea. Maybe I can refine it to use our two levels (if
the names of the flag files are well defined it may be simple enough to put
everything in the "enterprise" pom).
UPDATE: it does not work... I cannot put an <scm> within a <profile> :-(
was (Author: cadrian):
Good idea, thanks :-)
Although I still need a proper fix because we usually have two levels:
- our "enterprise" pom
- an "application head" containing all the modules an dinheritting from the
"enterprise" pom
- the application modules inheritting from the "application head"
Anyway, thanks for the idea. Maybe I can refine it to use our two levels (if
the names of the flag files are well defined it may be simple enough to put
everything in the "enterprise" pom).
> 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
