RE: site.xml for parent/child site which are siblings
There is another problem In that the children don't inherit the parents
site.xml correctly (or probably more accuratly the parents site.xml gets munged
when it is deployed.)
E.g we have a corporate pom which defines a site.xml which contains
menu ref=modules/
However when this gets deployed the menu ref=modules has gone. And as any
multi-module project that has the corporate pom as its parent doesn't show the
list of it's modules... Also it's missing any comments that where inside it.
Shouldn't the deploy deploy the descriptor as is?
E.g. the following:
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/DECORATION/1.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/DECORATION/1.0.0
http://maven.apache.org/xsd/decoration-1.0.0.xsd;
publishDate format=dd MMM /
body
breadcrumbs
item name=Infrastructure
href=http://xxx.yyy/some/path/default.aspx; /
item name=Runtime
href=http://xxx.yyy/some/other/path/default.aspx; /
/breadcrumbs
menu name=${project.name}
item name=Introduction href=index.html /
/menu
menu ref=parent /
menu ref=modules /
menu ref=reports /
/body
!-- a random comment --
/project
Becomes
?xml version=1.0 encoding=UTF-8?project
publishDate format=dd MMM /
body
breadcrumbs
item name=CAB Infrastructure
href=http://xxx.yyy/some/path/default.aspx; /
item name=Runtime href=http://xxx.yyy/some/other/path/default.aspx; /
/breadcrumbs
menu name=NDS CAB Maven build environment
item name=Introduction href=index.html /
/menu
menu ref=parent /
menu ref=reports /
/body
/project
Note that reports have gone and the name is now hard coded?
/James
-Original Message-
From: Benson Margulies [mailto:bimargul...@gmail.com]
Sent: 16 July 2009 00:29
To: Maven Users List
Subject: Re: site.xml for parent/child site which are siblings
I never attached the workaround to the JIRA. It is MSITE-409.
I'm trying to get organized to try to fix it. However, the
whole idea of a 'parent' link needs thought.
On Wed, Jul 15, 2009 at 2:54 PM, David C.
Hicksdhi...@i-hicks.org wrote:
Benson Margulies wrote:
I've filed a JIRA on this and also posted a workaround,
you have to
set up the URL for each project yourself. If you can't
find my posted
workaround I can post it again.
Benson, can you give us a JIRA number? I didn't find anything that
appeared to be the right one *and* had a workaround posted.
I could
have overlooked it, though.
Thanks!
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
**
This message is confidential and intended only for the addressee. If you have
received this message in error, please immediately notify the
postmas...@nds.com and delete it from your system as well as any copies. The
content of e-mails as well as traffic data may be monitored by NDS for
employment and security purposes. To protect the environment please do not
print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX,
United Kingdom. A company registered in England and Wales. Registered no.
3080780. VAT no. GB 603 8808 40-00
**
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: site.xml for parent/child site which are siblings
Thanks for the suggestion. I will definitely look into it. I tried just doing the following in my child site.xml: menu name=Used By item name=Avitek Parent href=../index.html/ /menu But this didn't work, it didn't even show the link. It's interesting, almost like the parent site.xml doesn't care about the child site.xmls. When I run $ mvn site:stage -DstagingDirectory=c:/beaportal/user_projects/workspaces/default/avitek/published-site/site It correctly takes my structure: -avitekApp (EAR) - pom.xml -avitekParent - src/site/site.xml (menu ref=modules name=Components/) - pom.xml -avitekWeb (WAR) - pom.xml And creates a structure of: -site - Parent Site - avitekApp Site - index.html - avitekWeb Site - index.html - index.html (with links to child sites) It's just that the child sites, don't show a link to the parent. I will try the information you provided in the responses to see if it works. When you run mvn site against a parent pom, does it use the parent site.xml and the child site.xmls to build the generated site? Thanks, Jay -- View this message in context: http://n2.nabble.com/site.xml-for-parent-child-site-which-are-siblings-tp3259842p3268421.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
Re: site.xml for parent/child site which are siblings
http://maven.apache.org/plugins/maven-site-plugin/faq.html#Why_dont_the_links_between_parent_and_child_modules_work_when_I_run_mvn_site 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] modelVersion4.0.0/modelVersion groupIdavitek-sample/groupId artifactIdparent/artifactId packagingpom/packaging version1.0-SNAPSHOT/version nameMaven 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 -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: site.xml for parent/child site which are siblings
I have been using menu ref, even as recently as two days ago in one of the multi-module project. Which version of site-plugin are you using? I'm using 2.0-beta-7. Do all the sibling modules have a site descriptor, with menu ref=parent? The breadcrumbs could be a problem in the default skin. I don't use the default skin, if you know velocity, you can download the default skin and peer into where things might be going wrong. (BTW, you can change the skin in site.xml) Thanks, mohan kr -Original Message- From: David C. Hicks [mailto:dhi...@i-hicks.org] Sent: Tuesday, July 14, 2009 6:57 PM To: Maven Users List Subject: Re: site.xml for parent/child site which are siblings I would really like to know if you're using the menu ref=parent/ and if it works?? I've been playing with it for the better part of two days, and I cannot get the parent link to show up at all. I've also been playing with breadcrumbs, but they appear to be severely broken - or, I just don't understand what they're supposed to be used for. :-) jaybytez wrote: 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] modelVersion4.0.0/modelVersion groupIdavitek-sample/groupId artifactIdparent/artifactId packagingpom/packaging version1.0-SNAPSHOT/version nameMaven 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: site.xml for parent/child site which are siblings
Okay...so I verified that each one of the sub projects has a site.xml with a menu ref=parent/ and I verified that I am running site-plugin 2.0-beta-7 and my sub projects still don't produce a link based on menu ref=parent/. I did not change the skin yet, but that should just be based on the CSS exposed...otherwise that shouldn't (I am assuming) effect the generated documentation. Any other thoughts? One other question two...if a project is used by multiple projects...does menu ref=parent/ show a link for all those parent projects? Thanks...jay I have been using menu ref, even as recently as two days ago in one of the multi-module project. Which version of site-plugin are you using? I'm using 2.0-beta-7. Do all the sibling modules have a site descriptor, with menu ref=parent? The breadcrumbs could be a problem in the default skin. I don't use the default skin, if you know velocity, you can download the default skin and peer into where things might be going wrong. (BTW, you can change the skin in site.xml) Thanks, mohan kr -- View this message in context: http://www.nabble.com/site.xml-for-parent-child-site-which-are-siblings-tp24489265p24500967.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
RE: site.xml for parent/child site which are siblings
The schema annotation says the following: xs:documentation source=descriptionA reference to a pre-defined menu, such as a codereports/code, codemodules/code or codeparentProject/code./xs:documentation So it says a value of parentProject as opposed to parent. -- View this message in context: http://www.nabble.com/site.xml-for-parent-child-site-which-are-siblings-tp24489265p24501723.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
Re: site.xml for parent/child site which are siblings
I was using 2.0-beta-7 until yesterday. I changed to 2.1. At the time, I only had a single site.xml at the parent level. It included the menu ref=parent/ tag. Assuming that all of the menu tags are inherited, I would have thought this would work. I've also tried it with site.xml in each module with equivalent tags. My project is set up standard, though. The parent project contains all of the modules, physically. Mohan KR wrote: I have been using menu ref, even as recently as two days ago in one of the multi-module project. Which version of site-plugin are you using? I'm using 2.0-beta-7. Do all the sibling modules have a site descriptor, with menu ref=parent? The breadcrumbs could be a problem in the default skin. I don't use the default skin, if you know velocity, you can download the default skin and peer into where things might be going wrong. (BTW, you can change the skin in site.xml) Thanks, mohan kr -Original Message- From: David C. Hicks [mailto:dhi...@i-hicks.org] Sent: Tuesday, July 14, 2009 6:57 PM To: Maven Users List Subject: Re: site.xml for parent/child site which are siblings I would really like to know if you're using the menu ref=parent/ and if it works?? I've been playing with it for the better part of two days, and I cannot get the parent link to show up at all. I've also been playing with breadcrumbs, but they appear to be severely broken - or, I just don't understand what they're supposed to be used for. :-) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site.xml for parent/child site which are siblings
I've filed a JIRA on this and also posted a workaround, you have to set up the URL for each project yourself. If you can't find my posted workaround I can post it again. On Wed, Jul 15, 2009 at 11:58 AM, jaybytezjayby...@gmail.com wrote: Okay...so I verified that each one of the sub projects has a site.xml with a menu ref=parent/ and I verified that I am running site-plugin 2.0-beta-7 and my sub projects still don't produce a link based on menu ref=parent/. I did not change the skin yet, but that should just be based on the CSS exposed...otherwise that shouldn't (I am assuming) effect the generated documentation. Any other thoughts? One other question two...if a project is used by multiple projects...does menu ref=parent/ show a link for all those parent projects? Thanks...jay I have been using menu ref, even as recently as two days ago in one of the multi-module project. Which version of site-plugin are you using? I'm using 2.0-beta-7. Do all the sibling modules have a site descriptor, with menu ref=parent? The breadcrumbs could be a problem in the default skin. I don't use the default skin, if you know velocity, you can download the default skin and peer into where things might be going wrong. (BTW, you can change the skin in site.xml) Thanks, mohan kr -- View this message in context: http://www.nabble.com/site.xml-for-parent-child-site-which-are-siblings-tp24489265p24500967.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site.xml for parent/child site which are siblings
Is this the post: http://n2.nabble.com/Site-generation-tutorials--td327.html#a3239539 Benson Margulies wrote: I've filed a JIRA on this and also posted a workaround, you have to set up the URL for each project yourself. If you can't find my posted workaround I can post it again. -- View this message in context: http://n2.nabble.com/site.xml-for-parent-child-site-which-are-siblings-tp3259842p3265147.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
Re: site.xml for parent/child site which are siblings
yes On Wed, Jul 15, 2009 at 2:50 PM, jaybytezjayby...@gmail.com wrote: Is this the post: http://n2.nabble.com/Site-generation-tutorials--td327.html#a3239539 Benson Margulies wrote: I've filed a JIRA on this and also posted a workaround, you have to set up the URL for each project yourself. If you can't find my posted workaround I can post it again. -- View this message in context: http://n2.nabble.com/site.xml-for-parent-child-site-which-are-siblings-tp3259842p3265147.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site.xml for parent/child site which are siblings
Thanks for the workaround, Benson. I was able to get it to work in my little test project. Now, I'm going after the big project. Benson Margulies wrote: yes On Wed, Jul 15, 2009 at 2:50 PM, jaybytezjayby...@gmail.com wrote: Is this the post: http://n2.nabble.com/Site-generation-tutorials--td327.html#a3239539 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site.xml for parent/child site which are siblings
Thanks for the workaround, Benson. I was able to get it to work in my little test project. Now, I'm going after the big project. Benson Margulies wrote: yes On Wed, Jul 15, 2009 at 2:50 PM, jaybytezjayby...@gmail.com wrote: Is this the post: http://n2.nabble.com/Site-generation-tutorials--td327.html#a3239539 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site.xml for parent/child site which are siblings
Benson Margulies wrote: I've filed a JIRA on this and also posted a workaround, you have to set up the URL for each project yourself. If you can't find my posted workaround I can post it again. Benson, can you give us a JIRA number? I didn't find anything that appeared to be the right one *and* had a workaround posted. I could have overlooked it, though. Thanks! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site.xml for parent/child site which are siblings
I never attached the workaround to the JIRA. It is MSITE-409. I'm trying to get organized to try to fix it. However, the whole idea of a 'parent' link needs thought. On Wed, Jul 15, 2009 at 2:54 PM, David C. Hicksdhi...@i-hicks.org wrote: Benson Margulies wrote: I've filed a JIRA on this and also posted a workaround, you have to set up the URL for each project yourself. If you can't find my posted workaround I can post it again. Benson, can you give us a JIRA number? I didn't find anything that appeared to be the right one *and* had a workaround posted. I could have overlooked it, though. Thanks! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site.xml for parent/child site which are siblings
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] modelVersion4.0.0/modelVersion groupIdavitek-sample/groupId artifactIdparent/artifactId packagingpom/packaging version1.0-SNAPSHOT/version nameMaven 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
Re: site.xml for parent/child site which are siblings
I would really like to know if you're using the menu ref=parent/ and if it works?? I've been playing with it for the better part of two days, and I cannot get the parent link to show up at all. I've also been playing with breadcrumbs, but they appear to be severely broken - or, I just don't understand what they're supposed to be used for. :-) jaybytez wrote: 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] modelVersion4.0.0/modelVersion groupIdavitek-sample/groupId artifactIdparent/artifactId packagingpom/packaging version1.0-SNAPSHOT/version nameMaven 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
