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/01/19 09:43:55 UTC
[jira] Created: (MSITE-458) Fixing the order of items in "Modules"
menu
Fixing the order of items in "Modules" menu
-------------------------------------------
Key: MSITE-458
URL: http://jira.codehaus.org/browse/MSITE-458
Project: Maven 2.x Site Plugin
Issue Type: New Feature
Components: multi module
Affects Versions: 2.1
Reporter: Andreas Sewe
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
[jira] Commented: (MSITE-458) Fixing the order of items in
"Modules" menu
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268278#action_268278 ]
Lukas Theussl commented on MSITE-458:
-------------------------------------
Herve: checking the attached test project with published site-plugin-2.3, the reactor build order is still second-first, but the order in the Modules menu of the generated site is first-second. So I consider this issue fixed.
> 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
[jira] Updated: (MSITE-458) Fixing the order of items in "Modules"
menu
Posted by "Andreas Sewe (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MSITE-458) Fixing the order of items in
"Modules" menu
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247170#action_247170 ]
Lukas Theussl commented on MSITE-458:
-------------------------------------
The order of items in the generated menu *is* the same as the order of <module> elements in your pom.
bq. This also means that the order of menu items depends on the module's dependencies;
I don't understand, why?
> 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
>
> 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
[jira] Commented: (MSITE-458) Fixing the order of items in
"Modules" menu
Posted by "Andreas Sewe (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268277#action_268277 ]
Andreas Sewe commented on MSITE-458:
------------------------------------
What for? Wasn't it fixed in the current 3.0-beta-4-SNAPSHOT?
> 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
[jira] Commented: (MSITE-458) Fixing the order of items in
"Modules" menu
Posted by "Andreas Sewe (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247222#action_247222 ]
Andreas Sewe commented on MSITE-458:
------------------------------------
I made the original report when using Maven 2 and version 2.1 of the {{maven-site-plugin}}. Since then I have moved on to Maven 3 and the corresponding version of plugin; alas, the problem persists. (If you have problems reproducing it, I'll attach a sample project -- but not tonight anymore)
> 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
>
> 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
[jira] Commented: (MSITE-458) Fixing the order of items in
"Modules" menu
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247291#action_247291 ]
Dennis Lundberg commented on MSITE-458:
---------------------------------------
OK thanks.
A sample project would be much appreciated.
> 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
>
> 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
[jira] Commented: (MSITE-458) Fixing the order of items in
"Modules" menu
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267658#action_267658 ]
Herve Boutemy commented on MSITE-458:
-------------------------------------
Andreas, can you open another issue with this problem?
> 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
[jira] Closed: (MSITE-458) Fixing the order of items in "Modules"
menu
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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: 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
>
> 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
[jira] Updated: (MSITE-458) Fixing the order of items in "Modules"
menu
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MSITE-458:
----------------------------------
Fix Version/s: 3.0-beta-4
> 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
[jira] Commented: (MSITE-458) Fixing the order of items in
"Modules" menu
Posted by "Andreas Sewe (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247219#action_247219 ]
Andreas Sewe commented on MSITE-458:
------------------------------------
No, as far as I can tell, the menu items are ordered with respect to the reactor build order, not with respect to the order of elements in the {{pom.xml}}. (I just tested this with Maven 3.0.1 and the version 3.0-beta-3 of the {{maven-site-plugin}}.) In general, the these two coincide only during {{--non-recursive}} builds.
> 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
>
> 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
[jira] Commented: (MSITE-458) Fixing the order of items in
"Modules" menu
Posted by "Andreas Sewe (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263070#action_263070 ]
Andreas Sewe commented on MSITE-458:
------------------------------------
Another side effect of using the reactor to determine the menu order (bit me today with 3.0-beta-3) is that the use of the {{resume-from}} option leads to incomplete "Modules" menus; this makes said option sadly unusable. So fixing this issue was more than a merely cosmetic change.
> 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
[jira] Commented: (MSITE-458) Fixing the order of items in
"Modules" menu
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247221#action_247221 ]
Dennis Lundberg commented on MSITE-458:
---------------------------------------
Andreas, you indicated when you created the issue that it affects version 2.1 of the Site Plugin. Is that correct or is this issue only for the 3.0 version of the Site Plugin together with Maven 3?
> 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
>
> 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
[jira] Commented: (MSITE-458) Fixing the order of items in
"Modules" menu
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ 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