Re: [gradle-dev] Getting a dependency tree

[Adam Murdoch]

Phil Messenger wrote: Hans, hdockter wrote: The BaseDependencyManager has a getIvy method. It is not exposed by the DependencyManager interface (because I consider the way we create the Ivy object not final. I have some open questions I have to file to the Ivy mailing list). Right. I've written a plugin which spits out a nice ASCII tree of the dependencies. Hooray! However, to do this I've had to use reflection to access the getIvy method on BaseDependencyManager (not a public method). Boo. I'm adding Graphviz dot output functionality so you can generate diagrams of your dependencies. Once this is done I'll contribute the code back. This would be fantastic. Would you prefer a new plugin, or an extension of some existing class/plugin? I think it belongs in a new plugin, as this kind of reporting cuts across all builds, regardless of which, if any, plugins are being used. It feels like this would be a build visualisation plugin, which initially would show the artifact dependencies of a project, but which could grow to show all types of dependencies, and also the structure of the build (e.g. like gradle -t but with more stuff). Adam --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email