Our approach is to have a dedicated documentation sub-project, with just xdocs. The multiproject parent project has little if anything in it, so the default navigation is fine. One of the links then leads to "Documentation". That project then has a customized navigation.xml linking together all the "root-level" documentation for the multiproject.
You mention that you "need" to have the documentation as part of the root web site. Would having it one link down but clearly labeled at the top of the sub-project list satisfy the need? Jay -----Original Message----- From: Phil Steitz [mailto:[EMAIL PROTECTED] Sent: Monday, August 08, 2005 8:54 PM To: Maven Users List Subject: Re: Multiproject site navigation question Wendy Smoak wrote: > From: "dan tran" <[EMAIL PROTECTED]> > >> Wendy, from maven-site-plugin doco, you dont create nagivation.xml at >> the root. Let the multiproejct:site generate it for you. > > > I have a bunch of "user-supplied documentation" that I need to link > in, and I need it to be part of the root website. AFAICT, to do that > I need to make a navigation.xml file. True? > > Thanks, FWIW, I struggled with this on a couple of projects and ended up finding it easier and more flexible to just maintain navigation.xml at each level. One thing that can make it slightly easier to manage the common elements (assuming you have these) is to use XML entities. Have a look at the commons-build project <http://svn.apache.org/repos/asf/jakarta/commons/proper/commons-build/> that defines a setup shared by Jakarta Commons components. The navigation.xml file there and in all of the commons subprojects refer to an external dtd that defines xml entities corresponding to the shared menu items. This is a little convoluted - maybe not maven "best practice" - but works and is not that hard to maintain once you have it set up. Phil --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
