Thanks for the reply Brett. I ran it both ways multiple times...there is no difference between using the default value for maven.build.dir in all projects or setting it to my preferred dir....the same problems occur.
I think the excludes is not needed; it is a remnant from my pasting of Fabrice's working settings. I have removed it, ran it again, and there was also no difference. The docs say that "maven.multiproject.navigation" defaults to aggregate. I have not set it anywhere. I remember reading about this setting from the archives too (I think from you! :-), and made sure I did not set it. Also, the links from the multiproject page point to the subprojects - they point to index.html files under the multiproject build dir! So it is not pointing to external references. -----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 31, 2005 10:10 PM To: Maven Users List Subject: Re: Multiproject plugin and "maven.build.dir" restrictions? > - Dashboard report is an empty page I have a feeling this one doesn't like build.dir changes, but I don't know enough about it (see the excludes you have, for example). > - Clicking subproject links from the multiproject page is invalid - > the pages do not exist (none of the standard HTML files are generated > in the subprojects). This is usually because you have the navigation set to independant, in which case the links are all external references based on the URL in the POM and you need to build the subproject sites individually using "site" instead of "multiproject:site" which is only used at th etop level. Do the above work when build.dir is the default? Cheers, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
