Sites and Inheritence

MavneMaven's support for sites that span multiple projects has generally been limited to date. The following are some features that will assist in this.

...

<menu name="Commons Common">
  <item ... />
</menu>

<menu name="Commons Specifics" inherit="bottom">
  <item ... />
</menu>

Including Generated Content

Currently there are elements like ${reports} and ${modules} in the site descriptor. These will be deprecated in favour of:

  <!-- Include all info and reports -->
  <menu ref="reports" />

  <menu ref="modules" />

~~TODO: not happy with this yet

Symmetric generation

When generating within the top level, content will be generated into the target/site location of the subproject, using the difference between the top level URL and the subproject's URL as the relative path to use. It will not be possible to navigate between the sites on the filesystem - you must push to staging to achieve this.

...

Skinning support will provided by a separate artifact that contains CSS, images and is unpakced unpacked over a site. It can optionally contain a replacement /META-INF/maven/site.vm velocity template for generating the final XHTML.

It is built as a normal JAR, using a custom packaging of "maven-skin". To configure the skin in the client, add it to the site plugindescriptor:

<plugin>
  <artifactId>maven-site-plugin</artifactId><project>
...
  <configuration><skin>
    <skinArtifact>
      <groupId>org.apache.maven.maven<skins</groupId>
      <artifactId>maven-sitedefault-skin</artifactId>
      <version>1.0-SNAPSHOT<0</version>
 <!--   </skinArtifact>optional -->
  </configuration>

Separation of user and developer documentation

...

skin>
...

Separation of different releases in documentation

see http://jira.codehaus.org/browse/MNG-41^{Image Removed}