Page History

...

• Inherited navigational elements
• Using submenus
• Ability to generate within the subproject, or at the top level and get the same results (with the exception of aggregated reports)
• No strict requirements on filesystem layout other than those that already exist for Maven projects
• Ability to aggregate reports (individual report technique out of scope here)
• Breadcrumbing
• Skinning

Proposed Solutions

Inherited Navigational Elements

...

Most of the work of this is covered in the individual plugins and the Maven Dashboard discussion. When running the site from the top level, it behaves as an @aggregator so that it is repsonsible for generating all of the child projects, rather than using the reactor to do so. This will enable final aggregation.

Skinning

Skinning support will provided by a separate artifact that contains CSS, images and is unpakced over a site.

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 plugin:

<plugin>
  <artifactId>maven-site-plugin</artifactId>
  <configuration>
    <skinArtifact>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-site-skin</artifactId>
      <version>1.0-SNAPSHOT</version>
    </skinArtifact>
  </configuration>