You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/04/13 15:19:15 UTC
[jira] [Commented] (MPOM-50) configure site staging for
multi-modules
[ https://issues.apache.org/jira/browse/MPOM-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967818#comment-13967818 ]
Hudson commented on MPOM-50:
----------------------------
SUCCESS: Integrated in maven-parent #163 (See [https://builds.apache.org/job/maven-parent/163/])
[MPOM-50] configure site staging for multi-modules (hboutemy: http://svn.apache.org/viewvc/?view=rev&rev=1586968)
* /maven/pom/trunk/maven/pom.xml
> configure site staging for multi-modules
> ----------------------------------------
>
> Key: MPOM-50
> URL: https://issues.apache.org/jira/browse/MPOM-50
> Project: Maven POMs
> Issue Type: Improvement
> Components: maven
> Affects Versions: MAVEN-24
> Reporter: Hervé Boutemy
> Assignee: Hervé Boutemy
> Fix For: MAVEN-25
>
>
> actually, for multi-modules, m-site-p topSiteURL has to be configured to avoid extra path in staged content:
> {code:xml} <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-site-plugin</artifactId>
> <configuration>
> <topSiteURL>scm:svn:https://svn.apache.org/repos/infra/websites/production/maven/content/${maven.site.path}</topSiteURL>
> </configuration>
> </plugin>{code}
> such configuration in parent pom would avoid copy/paste in every child
--
This message was sent by Atlassian JIRA
(v6.2#6252)