Karl Schaefer created MPIR-285:
----------------------------------
Summary: ModulesReport incorrectly contains indirect descendants
Key: MPIR-285
URL: https://jira.codehaus.org/browse/MPIR-285
Project: Maven Project Info Reports Plugin
Issue Type: Bug
Components: index, modules
Affects Versions: 2.7
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"
Reporter: Karl Schaefer
Attachments: patch.diff
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira