[MSITE-383] Problem using "super pom" as parent in multi module project

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0-beta-7
• Component/s: multi module
• Environment: Windows XP SP_2; JDK 1.5; Maven 2.0.9
• Assignee: Unassigned
• Reporter: Per Lindfors
• Created: 10/Feb/09 09:33
• Updated: 17/Feb/09 12:34
• Resolved: 17/Feb/09 12:34

Description

I'm trying to generate a site for my multimodule project with mvn site-deploy and with the following layout:

MyProj

• myproj-bl
• myproj-pl
• myproj-ear

In the case where each module refere to MyProj as <parent>, everything works fine, the module-links are listed in the index page for MyProj. But when I use the desired layout, where each module refere to a "super pom" as <parent>, the resulting site structure is different and the links to the modules are missing.

To me this is a bug when I dont find information saying that a module can have parent not beeing the "multimodule project"

To reproduce, use attched projects.

1. Unpack and build super-poms to your local repo.
2. Unpack and build myproj with mvn install site-deploy. The site will be deployed at c:/arkiv/proj/maven-site se root/pom.xml in super poms

Issue Links

• duplicates: MSITE-129 modules list empty if modules don't use this project as parent in reactor build