You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Andrew Robinson <an...@gmail.com> on 2007/04/30 15:43:28 UTC
[OT] Maven site advice?
Sorry for the off-topic, but it looks like myfaces has done a nice
implementation with maven 2 to publish its web site. My problem is
that site:deploy ruined my relative links and that a <parent> pom.xml
tag causes heartache for people trying to build my project.
Last night I tried to publish the jsf-comp web site using maven 2 with
a "<modules>" tag in the pom.xml of the site, and a "<parent>" tag in
my project's pom.xml. The projects are in two separate directories,
not directly under one another:
jsf-comp/site/jsf-comp/pom.xml
jsf-comp/facelets/annotation-deployment/pom.xml
I tried in the child:
<parent>
<groupId>net.sf.jsf-comp</groupId>
<artifactId>jsf-comp</artifactId>
<version>0.0.3</version>
<relativePath>../../site/jsf-comp/</relativePath>
</parent>
And in the parent:
<modules>
<module>../../facelets/annotation-deployment</module>
</modules>
<distributionManagement>
<site>
<id>sf.net</id>
<url>scp://shell.sf.net/home/groups/j/js/jsf-comp/htdocs</url>
</site>
</distributionManagement>
And when I did a mvn site:stage it worked great. However, when I did a
site:deploy the parent & modules links were broken.
The <menu ref="modules" /> produced:
http://jsf-comp.sourceforge.net/jsf-comp-facelets-deployment/index.html/index.html
and the <menu ref="parent" /> didn't create a link at all.
Also, I don't know if this is the best way to setup the project, as
people trying to build my project using maven must download the "site"
svn module.
Would someone be so kind as to recommend a way to get the ability to
publish a site, pulling in child maven sites, but without this bad
relative paths that I created?
Thanks for any assistance,
Andrew