[MPIR-285] ModulesReport incorrectly contains indirect descendants

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.7
• Component/s: index, modules

Environment

Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 08:51:28-0500)
Maven home: C:\apache-maven-3.0.5\bin\..
Java version: 1.6.0_32, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_32\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"

• Flags: Patch
• Assignee: Unassigned
• Reporter: Karl Schaefer
• Created: 07/Aug/13 13:08
• Updated: 05/Apr/15 14:53
• Resolved: 28/Oct/14 13:42

Description

The modules listed for a multi-module project that contains multi-modules projects are completely out of sorts.

The modules.html and index.html contain all descendant modules, even those that are not direct decendents. Once the site is staged, any module link that is not a direct descendent of the base module is broken. The correct solution is to not show modules that are not direct descendents. Theorectically, you'd want to dig into the child module to see its children in lieu of this flattening.

Likely related to MPIR-273 and MPIR-279 and caused by the fix to MPIR-229

The unit test files were also buggy, so the included patch makes modifications to them. To see failing results run the modified code sans changes to ModulesReport.

Issue Links

• duplicates: MPIR-279 Wrong hyperlinks on index and modules page