Hi,
On May 7, 2009, at 4:56 PM, Narco wrote:
Hello!
Imo it is confusing that sub-projects are executed in alphabetical
order. It
would be nice to run them simply in order which they are defined after
include statement if no other project dependency rules exists. What
do You
think?
We have discussed something similar in regard to dependsOn relations
between tasks. We came to the conclusion that things can become messy
and hard to comprehend if we consider the order of declaration.
Probably the same reasoning applies to projects.
You may file a Jira issue so that we don't forget to discuss project
ordering for 0.7.
Thanks
- Hans
--
View this message in context:
http://www.nabble.com/projects-execution-order-in-multi-project-build-tp23428510p23428510.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
