Done: http://jira.codehaus.org/browse/MSITE-420
I think the problem is that site doesn't honor all the options doxia makes available. -----Original Message----- From: Lukas Theussl [mailto:[email protected]] Sent: Friday, July 31, 2009 4:03 AM To: Maven Users List Subject: Re: Site inheritance I am currently reviewing the site plugin to get it ready for another release (might take a while still, though). If you find anything that's not working the way you expect it, please file an issue in jira and attach a simple test project (or a patch!). There are a couple of issues open regarding inheritance [1] even though they are not on my short list for this release. Cheers, -Lukas [1] http://jira.codehaus.org/browse/MSITE/component/12943 EJ Ciramella wrote: > Maybe I got ahead of myself - I tried setting (in the parent project > site descriptor) the "inheritAsRef='true'", but no matter what that's > set to, in the child site output, there are links back to the parent > project. > > All I want is the structure provided by the parent's project. I want > the menu bits but the actual apt file will live in the child projects. > Is this possible? > > -----Original Message----- > From: EJ Ciramella [mailto:[email protected]] > Sent: Friday, July 31, 2009 12:01 AM > To: Maven Users List > Subject: RE: Site inheritance > > Lol - ok, I think I figured this out... > > In the _parent_ project's site descriptor, I defined a menu as > "inherit"-able and now it's showing up in the child site output. > > This should be more clearly spelled out in the site plugin doc set... > > -----Original Message----- > From: EJ Ciramella [mailto:[email protected]] > Sent: Thursday, July 30, 2009 8:36 PM > To: [email protected] > Subject: Site inheritance > > Hello all - > > I'm forging forward (after the semi-informal poll about site doc > format > options) with a very vanillia "apt" set up for now and I'm trying to > inherit a "skeleton" site project. > > I can see this is possible: > > http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescrip > to > r.html (look at the inheritance bit) > > But, does this only work in parent->child relationships? Can I just > put a dependency on a site-only project and pull down the site descriptor? > > We have four distinct types of maven based projects. For each of > these, there is a distinct set of links people should be providing for > each app. > > Instead of copy/pasting a site descriptor everywhere, I'd prefer to > create skeletons and just depend on them as needed - is this just > impossible? > > What about for individual pages? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
