Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <1883999863.1254769351377.JavaMail.jira@brutus>
Date: Mon, 5 Oct 2009 12:02:31 -0700 (PDT)
From: "Ivica Loncar (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Commented: (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:comment-tabpanel&focusedCommentId=12762311#action_12762311 ] 

Ivica Loncar commented on IVYDE-208:
------------------------------------

h2. Scroll

I thought it would be nice to have scrollable zoom but I guess we can live without it for now.

h2. Search behaviour

Some of our projects have a lot of dependencies and graphs tend to get wide so It's hard to find some of the websphere jars if you don't remember exact name.
I agree... it's not that important feature.

h2. "Focus on file" behaviour

What can be done with configurations that are not exposed as eclipse classpath containers? Can we get them visualized also?


> 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, 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.