On 25/11/2010, at 2:09 AM, Gretar Arnason wrote:
> Hi, I've was just trying out something and was wondering if the following is
> an expected behavior (using 0.9-rc-2)
>
> in build.gradle file:
>
> task a << {
> println "a"
> }
>
> task b << {
> println "b"
> }
>
> task c (dependsOn: ["b","a"]) << {
> println "c"
> }
>
>
> gives me the the output when running >gradle -q c:
> a
> b
> c
>
> I was expecting to see:
> b
> a
> c
>
> Is my intuition just wrong?
> I would think that the order of dependencies should be respected if the tasks
> being depended on do not have any dependencies defined themselves.
> If I'm wrong about this can someone then explain here to me then what I
> should expect and why?
> How could I get the same effect without adding explicit dependency between a
> and b?
Do you have a more concrete example of what you're trying to achieve? Perhaps
you could explain what the problem is that you are trying to solve with
dependency ordering.
>
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
CTO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz
