[
http://jira.codehaus.org/browse/MSITE-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165695#action_165695
]
Dennis Lundberg commented on MSITE-383:
---------------------------------------
Can I close this a a duplicate Per?
> Problem using "super pom" as parent in multi module project
> -----------------------------------------------------------
>
> Key: MSITE-383
> URL: http://jira.codehaus.org/browse/MSITE-383
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: multi module
> Affects Versions: 2.0-beta-7
> Environment: Windows XP SP_2
> JDK 1.5
> Maven 2.0.9
> Reporter: Per Lindfors
> Attachments: MyProj.zip, super-poms.zip
>
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
