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 <[email protected]> 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 common use case), and it is very easy to code up their behaviour > in the build script if you do happen to need it. And so, I'd like to remove > them (via deprecation, of course). > > Thoughts? > > > -- > Adam Murdoch > Gradle Co-founder > http://www.gradle.org > VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting > http://www.gradleware.com > -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/3xugrbk I work here; http://tinyurl.com/6a2pl4j I relax here; http://tinyurl.com/2cgsug --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
