You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Nicolas Lalevée (JIRA)" <ji...@apache.org> on 2011/04/25 12:47:05 UTC

[jira] [Resolved] (IVYDE-208) Ivy Resolve Visualizer

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

Nicolas Lalevée resolved IVYDE-208.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: trunk
         Assignee: Nicolas Lalevée

I finally integrated the patch into the trunk. I made it a separate plugin so it can be optionally installed, since it requires additional dependencies (zest).

> Ivy Resolve Visualizer
> ----------------------
>
>                 Key: IVYDE-208
>                 URL: https://issues.apache.org/jira/browse/IVYDE-208
>             Project: IvyDE
>          Issue Type: New Feature
>            Reporter: Jon Schneider
>            Assignee: Nicolas Lalevée
>             Fix For: trunk
>
>         Attachments: ZoomableComposite.java, evicted.gif, focus.gif, ivy.xml, ivyde-208.patch, 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, screenshot-6.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira