Maven 2.x and 3.x Site Plugin

multi module reporting - main page doesn't show links to contained modules

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: multi module
  • Labels:
    None
  • Number of attachments :
    0

Description

In a multi module project, the "site" generates a main page index.html, which has the contained modules on the upper left hand corner in bold face. These should be hyperlinks to the actual module's index.html

Issue Links

Activity

Hide
John Allen added a comment -

If you mean modules menu, in the top LHS (using the default site.xml) then yes they should be links and if they're not something else is afoot. Note that those module links should be on every generated page, not just the index.html one.

Show
John Allen added a comment - If you mean modules menu, in the top LHS (using the default site.xml) then yes they should be links and if they're not something else is afoot. Note that those module links should be on every generated page, not just the index.html one.
Hide
Dennis Lundberg added a comment -

The links to the modules only work if you run ' mvn site:stage'.

Show
Dennis Lundberg added a comment - The links to the modules only work if you run ' mvn site:stage'.
Hide
Mykel Alvis added a comment -

I'm having this issue, as well.
site:stage does not produce a working list of modules.

So I tried a site:stage-deploy, which then asked me for a password for the local user on my box (mykel) , NOT the user that I deploy remotely via scp with (localbuild) according to my settings.xml, which specifies user localbuild. Maybe site:stage-deploy ignores the settings in settings.xml?

In any case, the modules list in the generated html is still empty. site:stage has no effect on my particular multi-module build. My modules list is still empty.

Show
Mykel Alvis added a comment - I'm having this issue, as well. site:stage does not produce a working list of modules. So I tried a site:stage-deploy, which then asked me for a password for the local user on my box (mykel) , NOT the user that I deploy remotely via scp with (localbuild) according to my settings.xml, which specifies user localbuild. Maybe site:stage-deploy ignores the settings in settings.xml? In any case, the modules list in the generated html is still empty. site:stage has no effect on my particular multi-module build. My modules list is still empty.
Hide
John Allen added a comment -

dup of other 'empty modules menu'?

Show
John Allen added a comment - dup of other 'empty modules menu'?

People

Vote (3)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved: