[
http://jira.codehaus.org/browse/MSITE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268287#action_268287
]
Lukas Theussl commented on MSITE-458:
-------------------------------------
I added the test project as an IT:
[r1126918|http://svn.apache.org/viewvc?rev=1126918&view=rev]
> 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
> Assignee: Lukas Theussl
> Fix For: 2.3, 3.0-beta-4
>
> 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
