Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
maven-doxia-tools-1.0.1
-
None
-
Patch
Description
Some of this is my fauilt as the code in question came from some of the patch wsork i did on 2.0-beta-6.
Basically populateModulesMenuItemsFromReactorProjects uses the following to determine if a project in the reactor is a module of the current project:
if ( reactorProject != null && reactorProject.getParent() != null && project.getArtifactId().equals( reactorProject.getParent().getArtifactId() ) )
This is invalid. A module != child
This needs to be changed to a check that's based upon the project's location, for that's all we've got when it comes to determining the backref relationship of a module to its aggregator (the enclosing project that refered to the module via a <module> element.
Patch will follow
Attachments
Attachments
Issue Links
- is depended upon by
-
MSITE-129 modules list empty if modules don't use this project as parent in reactor build
- Closed
- relates to
-
MSITE-163 The modules menu is not inherited if the parent project has no modules of its own
- Closed
- supercedes
-
MSITE-136 when inheriting site.xml the <menu ref='parent'> expands to a menu with links for *all* ancestors and not just the immediate parent
- Closed