Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <1292325990.1254579863537.JavaMail.jira@brutus>
Date: Sat, 3 Oct 2009 07:24:23 -0700 (PDT)
From: "Jon Schneider (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Updated: (IVYDE-208) Ivy Resolve Visualizer
In-Reply-To: <479967924.1254400283987.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/IVYDE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jon Schneider updated IVYDE-208:
--------------------------------

    Attachment: ivyde-208.patch

> Ivy Resolve Visualizer
> ----------------------
>
>                 Key: IVYDE-208
>                 URL: https://issues.apache.org/jira/browse/IVYDE-208
>             Project: IvyDE
>          Issue Type: New Feature
>            Reporter: Jon Schneider
>         Attachments: evicted.gif, focus.gif, ivyde-208.patch, ivyde-208.patch, ivyde-208.patch, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, screenshot-5.jpg
>
>
> I am kind of excited about this one.  I would like to be able to see the resolve report depicted graphically, showing me clearly how particular dependencies wound up on the classpath, what nodes got evicted, what dependencies a particular transitive dependency has, etc etc.  Ivy can sometimes fall into the category of "automagically" doing so much for us on the classpath, that developers can take it for granted.  Especially when a version conflict arises out of a resolution (by which two different revisions are resolved that aren't under the same eviction context), I see developers getting very confused.  I hope this visualization will help them understand.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.