Maven 2.x and 3.x Site Plugin

Module navigation entries point to index.html not <moduleName>/index.html

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Cannot Reproduce
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: multi module
  • Labels:
    None
  • Environment:
    Intel box running Windows XP
  • Testcase included:
    yes
  • Number of attachments :
    1

Description

I am using Maven version 2.0.4

I am experimenting with Maven to see if it will suit my organizations needs and I have created a simple example that looks like the following:
App1Pom
+ App1Ear
+ App1Jar

(pom.xml snippet)
<modules>
<module>App1Ear</module>
<module>App1Jar</module>
</modules>

When I generate the site using mvn site, the "About" page for App1Pom shows the two modules in the module section of the navigation, but neither has an anchor. When I navigate to another section, both module entries will now contain an anchor that points to index.html.
(index.html snippet)
<h5>Modules</h5>
<ul>

<li class="none">
<strong>App1Ear</strong>
</li>

<li class="none">
<strong>App1Jar</strong>
</li>
</ul>

(project-info.html snippet)
<h5>Modules</h5>
<ul>

<li class="none">
<a href="index.html">App1Ear</a>
</li>

<li class="none">
<a href="index.html">App1Jar</a>
</li>
</ul>

When I generate the site using mvn site:stage, the navigation section contains the correct entries of App1Ear/index.html and App1Jar/index.html.

(index.html snippet)
<h5>Modules</h5>
<ul>

<li class="none">
<a href="App1Ear/index.html">App1Ear</a>
</li>

<li class="none">
<a href="App1Jar/index.html">App1Jar</a>
</li>
</ul>

I have tried to review the current bug list to see if this problem has already been reported, but I was not able to see an entry that describes this situation. If I have a usage problem please point me to some documentation that can help me understand.

Thanks.
Dale Chapman.

Activity

Hide
Sam Wilson added a comment -

I am having the same issue.

In some cases this is working for me and in others it is not. I'm trying to see if I can figure out what is different that is causing the failure.

Very frustrating.

Show
Sam Wilson added a comment - I am having the same issue. In some cases this is working for me and in others it is not. I'm trying to see if I can figure out what is different that is causing the failure. Very frustrating.
Hide
John Allen added a comment - - edited

Probably related to the way the modules have been found (ie via reactor, via filesystem or via the repository). In some cases (namely non-reactor) a module project wont be fully interpolated (and indeed inheritance composition may not have occured either, cant remember). Best to explicitly define URLs (and thus distroManagement.site.url) for all your projects if you do non-reactor based site builds

Show
John Allen added a comment - - edited Probably related to the way the modules have been found (ie via reactor, via filesystem or via the repository). In some cases (namely non-reactor) a module project wont be fully interpolated (and indeed inheritance composition may not have occured either, cant remember). Best to explicitly define URLs (and thus distroManagement.site.url) for all your projects if you do non-reactor based site builds
Hide
Dennis Lundberg added a comment -

Sample project that works for me using Maven 2.0.8 and the latest 2.0-beta-7-SNAPSHOT of the Site plugin.

Show
Dennis Lundberg added a comment - Sample project that works for me using Maven 2.0.8 and the latest 2.0-beta-7-SNAPSHOT of the Site plugin.

People

Vote (2)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved: