Looks like it works if use the following at the command line: $ mvn site:stage -DstagingDirectory=c:/beaportal/user_projects/workspaces/default/avitek/published-site/site
Is it best to build a site to a staging area and then push that staging area to a remote server? It appears to correctly have created the site with no modifications to POMs. My only outstanding question now is, the menu ref="parent" is not working for me in the child poms...any reason for this? Thanks - jay jaybytez wrote: > > I have the following structure for my app: > avitek > -avitekApp (EAR) > - pom.xml > -avitekParent > - src/site/site.xml > - pom.xml > -avitekWeb (WAR) > - pom.xml > > My parent pom.xml in avitekParent says the following: > [code] > <modelVersion>4.0.0</modelVersion> > <groupId>avitek-sample</groupId> > <artifactId>parent</artifactId> > <packaging>pom</packaging> > <version>1.0-SNAPSHOT</version> > <name>Maven 2 Portal Sample</name> > <modules> > <module>../avitekApp</module> > <module>../avitekWeb</module> > </modules> > [/code] > > Then my site.xml for the parent (avitekParent) says this: > [code] > <menu ref="modules" name="Components"/> > [/code] > > So when I open: > C:\beaportal\user_projects\workspaces\default\avitek\avitekParent\target\site\index.html > It gives me links to my child projects (modules), but the urls that get > generated into the html are like this: > C:\beaportal\user_projects\workspaces\default\avitek\avitekParent\target\site\avitekWeb\index.html > And they need to look like: > C:\beaportal\user_projects\workspaces\default\avitek\avitekWeb\target\site\index.html > > Any thoughts or suggestions? > > Thanks...jay > -- View this message in context: http://www.nabble.com/site.xml-for-parent-child-site-which-are-siblings-tp24489265p24489751.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
