When building a maven site for a multi-module project the html content is built into the following....

./target/site/*
./module-a/target/site/*
./module-a/target/site/*

However, when the site is deployed it is restructured as:

./*.html
./module-a/*.html
./module-b/*.html

Since the filesystem's are not the same, the href links will be broken on at least one (the first one)

href='./module-a/blah.html' != href='../../module-a/target/site/blah.html'

Currently the jenkin 'maven generated site' link (per maven job) provides a link to the broken parent/root pom's site. All links to child modules, and those in between child modules are broken.

To fix this, I would suggest that the maven support automatically set the parameters (relative to the jenkins workspace) for site:stage and/or site:stage-deploy so that the site is built/deployed with a destination that will be hosted/published by jenkins.