You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andreas Sewe (JIRA)" <ji...@codehaus.org> on 2010/12/13 13:53:58 UTC

[jira] Updated: (MSITE-458) Fixing the order of items in "Modules" menu

     [ http://jira.codehaus.org/browse/MSITE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Sewe updated MSITE-458:
-------------------------------

    Attachment: demo.tar.gz

Despite the {{<module>}} ordering of {{first}}, {{second}} the order of menu items generated upon a {{mvn clean install site}} reflects the reactor build order:

{quote}
[INFO] Reactor Build Order:
[INFO] 
[INFO] Has modules list
[INFO] Should be second in Modules list
[INFO] Should be first in Modules list
{quote}

(Tested using Maven 3.0.1 and 2.2.1; if you want to use the latter, remove the {{pluginManagment}} section in the aggregator POM.)

> Fixing the order of items in "Modules" menu
> -------------------------------------------
>
>                 Key: MSITE-458
>                 URL: http://jira.codehaus.org/browse/MSITE-458
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: New Feature
>          Components: multi module
>    Affects Versions: 2.1
>            Reporter: Andreas Sewe
>         Attachments: demo.tar.gz
>
>
> Currently, it is impossible to influence the order in which the "Modules" show up in a generated site's menu when including them like this in the site descriptor:
> bq. <menu ref="modules"/>
> As far as I can tell, the order of items in the menu depends on the order in which Maven builds the modules -- and this does not always put the most important module at the top of the list. In fact, the top of the list is in all likelihood occupied by various low-level infrastructure modules; the high-level, user-visible modules typically come much later. :-( 
> This also means that the order of menu items depends on the module's dependencies; thus, this can result in unforeseen changes to the *site* when one module's *build* changes. Why doesn't Maven simply use the order of the {{module}} elements? That would be simple and predictable.

-- 
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