The plugin-generated main project pages automatically gets links down to the sub-projects via the multiproject plugin, showing the sub-projects in the side navigation bar. This menu above adds links back from the sub-projects to the main in the side navigation bar (would be nice for the multiproject to add this itself in a future release)
The plugin is able to generate links for you, but the usage of this feature is not really straightforward ATM. You have two options
1) If you don't have any custom xdocs in your top level project delete the navigation.xml file - you'll get one containting 'Projects' menu with linkst to the subprojects, and well known 'Project docmentation' for the top level project.
2) If you have the xdocs in the top level project you must provide a velocity template for generating the navigation with subproject links. You need to grab one of the files from http://cvs.apache.org/viewcvs/maven/src/plugins-build/multiproject/src/plugin-resources/templates/ and fill them in with your custom links. You need to put your copy into the ${basedir}/multiproject/navigation.xml location. I personally think it should better be ${basedir}/xdocs/multiproject-navigation.xml, I'm going to file an issue for that.
a). Personally I think that in the multiproject plugin, it would be better to use project 'id' rather than 'name' in the generation of directories under "docs/multiproject". The 'name' can be much longer, whereas the id will be more concise and less likely to change - so for example in my example above I could have just put 'App' instead of 'The Application'.
See http://jira.codehaus.org/secure/ViewIssue.jspa?id=11325
b). The generation of the site seems to have changed in beta 10 (note definite on this), but if i run a "maven site:generate" it does the compile AFTER the javadoc. The only problem here is that I use xdoclet to generate a series of interface classes, and hence these don't make their way into the Javadoc since they are generated after the javadoc (and hence javadoc complains about all sorts of missing classes). Seems logical to change this so that it does a compile first of all ... any problems with doing this ?
I've never used xdoclet but I think it's a major issue for anyone who is. Consider filing a bug report. As a stop-gap solution you should be able to fix it in your maven.xml with a <preGoal> tag.
c). How do I get anything to appear under the "Project Info"->"Issue Tracking" link ? Is there a section in project.xml for this ? (couldnt find one).
<project> .... <issueTrackingUrl>the url</issueTrackingUrl> </project>
d). Can I get rid of the "Development Process" link ? (I can change the URL I know, but I want to remove it totally :-)).
I see you've filed a bug for that. If noone picks it up, I'd recommend approaching Ben or d'Ion personally - they have a lot of experience with site generation stuff.
[e. had to omit the main project from the multiproject generation because of the bug spotted by Rafal Krzewski. - will be perfect when we can enable this again, because at the moment it is ignoring generating my own documentation for the top-level project].
Your documentation is processed. The issue was showing up if you told
maven to process it twice: as the super project, and one of the sub projects at the same time. Just look into target/docs and find the
generated .html files. The problem is that links to the won't show up
unless you provide ${basedir}/multiproject/navigation.xml file (see
above).
I have another idea for solving the issue of navigation generation.
Multiproject plugin could add a <subprojects-menu> tag to the navigation.xml schema. The menu would be written to target/generated-xdocs/subprojects-menu.xml and itegrated in the proper place by the site's stylesheet in the xdoc plugin. I think this would
be a much cleaner solution that what we have now. I'll look into
implementing this, but I'll need to learn more about manipulating xml/DOM under jelly so this will take some time, unless someone more
experienced steps in to help.
R.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
