On Oct 29, 2008, at 10:31 PM, Phil Messenger wrote:
hdockter wrote:
For 0.6 we want to generate a dependency graph report.
This what I'm trying to achieve... I've had some whinging from my
team that
it's hard to track down broken transitive dependencies!
I can fully understand them :). This is something I'm also missing in
my work as a Gradle user. Not so much for a single project build like
the Gradle build. But in larger multi-project build this is an
important feature.
hdockter wrote:
Unfortunately the logic for this is hidden in the Ant Ivy tasks
and not
accessible
via the Ivy API. So we have to do some work here and I guess we might
as well provide a method then, which returns a tree of dependencies.
Yup, I had a look at the Ivy Ant tasks and they parse the XML the Ivy
generates, which is pretty poor. I'm probably going to need to do
this for
work shortly so I'll contribute the code back.
I guess even extracting the code how Ivy is doing it in the Ant tasks
would be a big step forward.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
