Hi developers out there, Perhaps this is not the correct place to ask, but as I am not sure otherwise, I do ask here. Please tell me if i should direct such a query elsewhere in future.
I have a question regarding the somewhat unexpected order of execution of dependent tasks. There seems to be an issue lodged here: http://jira.codehaus.org/browse/GRADLE-427 and others have asked about it, here http://gradle.1045684.n5.nabble.com/dependsOn-problem-td2260570.html I notice that I am running version 1.7.6, and the issue exists The issue, so far as I can tell, was scheduled for version 1.7.1 It seems like a relatively simple fix. So, I assume that for whatever reason, the developers don't really want to fix it. Or rather, I suspect, a better solution is being considered? Is there any idea of how dependsOn for tasks will or should work in the future? For myself, it was quite unexpected that it didn't work like ANT, i.e.., tasks run in the order they are given. However, this perhaps matters to me because I am still thinking more 'ant' like, and not yet enough 'gradle or groovy' like. In fact, I assume that the developers didn't immediately realize this problem, that they have a different way of designing a script whereby this dependsOn order is not an issue? If so, can they recommend any hints .... a way of thinking when designing a simple script, that would help me also help me avoid this dependsOn order problem. I do not want to rely on the fact that at the moment it seems alphabetical. Not only is this (so far as I can tell) not officially documented, it would be a hassle to ensure my naming of tasks is adhering to this scheme. For it comes up often. ..... I want to do something, and I have to consider that I can not rely on the order of events. Kind Regards, Sean --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
