maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kek (JIRA)" <>
Subject [jira] Commented: (MSITE-438) <menu ref="modules"/> dropped from site.xml for pom.xml without <modules> section
Date Tue, 01 Dec 2009 17:04:55 GMT


Kek commented on MSITE-438:

I found new workaround. Simly define 

    <module></module> <!-- workaround for

to pom.xml for parent-pom. This gives me the requested result.

> <menu ref="modules"/> dropped from site.xml for  pom.xml without <modules>
> ----------------------------------------------------------------------------------
>                 Key: MSITE-438
>                 URL:
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>          Components: inheritance, multi module
>    Affects Versions: 2.0.1
>         Environment: Windows XP, CentOS Linux, Maven 2.2.1, Sun JDK 1.6.0_u17
>            Reporter: Kek
>         Attachments:
> We have common "pom-parent" artifact that defines repositories, pluginsManagement, distribution,
etc. And there is defined the site.xml descriptor too. 
> The site.xml lokks like:
>   <body>
>     <menu ref="parent"/>
>     <menu ref="modules"/>
>     <menu ref="reports"/>
>   </body>
> but when we build this artifact and deploy it to the repository, there is automaticaly
generated and uploaded different site descriptor "pom-parent-1.0.0-site.xml" that contains
>   <body>
>     <menu ref="parent" />
>     <menu ref="reports" />
>   </body>
> The "modules" menu was droped by maven.
> After some investigation I found that the "modules" menu section is always dropped, when
the pom.xml for pom-parent does not contains any submodule definition
>    <modules>
>      <module>some-submodule</module>
>    </modules>
> But I don't want to specify any submodule for this common pom because it is used as "abstract"
parent for all company projects. We want to have only one central site.xml descriptor definition
managed in "pom-parent" project and avoid its duplication in each inherited project. 
> The workaround is create some "dummy-submodule" under "pom-parent" and define the <modules>
section in pom.xml or define the site.xml descriptor for each inherited project.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message