-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Platform: PC, OS: Linux
When Maven2 project is setup to generate the Maven site, Hudson displays
'Maven-generated site' links on the project page. If the project is a
multi-module Maven project then that link points to a site generated for one of
the modules and not the project itself.
Maven will generate the sites individually for every module but links between
parent modules and child modules will only work after the site has been deployed
or staged.
As a suggestion, the 'Maven-generated site' link should point to that module's site.
- is duplicated by
-
JENKINS-4601 MavenSiteArchiver performs incorrectly on multi-module projects
-
- Closed
-
- is related to
-
JENKINS-22673 Sites for nested Maven multi-module projects deeper than one level are archived flat
-
- Resolved
-
I would like to hijack this bug
The first issue (project shows the site of the last generated module) is
actually a duplicate of bug 2245, and the patch solves the problem, including
navigation to the modules in the project's Maven site.
However, I think that Hudson should call the site generation for the project and
all of its modules separately and store the Maven site separately. So, the
project would have a "Maven generated site", and then every module should also
show its own "Maven generated site".