On 20/10/2011, at 8:51 PM, Luke Daley wrote: > Following on from previous email… > > Why doesn't `gradle dependencies` act like, say, `gradle clean` and invoke > the task on all sub projects as well?
It used to, and by doing this on any real project, you end up with pages of output, with the actual information you're after buried deep in there. Having it report on just the current project was a cheap solution, but not a particularly good one. I think we want some better way to express what you're interested in, so we can show more focused information. Two important use cases, I think: * show me the (compile) classpath of project x, and why each jar is (or is not) in there * show me the (compile-time) project dependency graph for every project reachable from project x I'd be tempted to split this into 2 separate tasks. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
