maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukas Theussl (JIRA)" <>
Subject [jira] Closed: (MSITE-458) Fixing the order of items in "Modules" menu
Date Tue, 14 Dec 2010 10:13:02 GMT


Lukas Theussl closed MSITE-458.

       Resolution: Fixed
    Fix Version/s: 2.3
         Assignee: Lukas Theussl

Thanks for the test. Should be fixed with MSHARED-173.

> Fixing the order of items in "Modules" menu
> -------------------------------------------
>                 Key: MSITE-458
>                 URL:
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: New Feature
>          Components: multi module
>    Affects Versions: 2.1
>            Reporter: Andreas Sewe
>            Assignee: Lukas Theussl
>             Fix For: 2.3
>         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:
For more information on JIRA, see:


View raw message