I dont like those methods, either. Using them feels like a workaround, not
a proper solution. However, i'm wondering what would be the actual
replacement in some builds...
Cheers!
> Thoughts?
>
>
> --
> Adam Murdoch
> Gradle Co-founder
> http://www.gradle.org
> VP of Engineering, Gradleware Inc.
Can you explain how to do instead??
Because if I remove my dependsOnChildren() the build fails drastically
But I have never understood why, so in principle I think you have a
point, I just want to know what I need to be prepared of.
Thanks
On Mon, Jan 16, 2012 at 12:21 PM, Adam Murdoch
wrot
On 16/01/2012, at 4:21 AM, Adam Murdoch wrote:
>
> I'd like to remove Project.dependsOn(), along with getDependsOnProjects(),
> childrenDependOnMe() and dependsOnChildren(). These methods don't do anything
> like what people expect (ie they are confusing without really solving any
> commo
I'd like to remove Project.dependsOn(), along with getDependsOnProjects(),
childrenDependOnMe() and dependsOnChildren(). These methods don't do anything
like what people expect (ie they are confusing without really solving any
common use case), and it is very easy to code up their behaviour in
