Paolo wrote: > However, it might be handy to publish Javadocs, etc. There is already a mechanism in the Apache CMS for adding Javadocs. It just needs the build process, or some scripted process, to generate a .jar of the JavaDocs, and that to be committed to the staging site svn. A CMS script then unpacks the jar when staging is published, and positions the unpacked documentation on the external site. This saves having a bazillion separate Javadoc files in the SVN, but keeps us having a single documentation process.
That's not to say that some aspects of mvn site might be useful, if we wanted to, say, publish test coverage results. But that's a step beyond what we do at the moment. Ian
