ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Schneider (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVYDE-208) Ivy Resolve Visualizer
Date Sat, 03 Oct 2009 14:30:23 GMT

    [ https://issues.apache.org/jira/browse/IVYDE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761889#action_12761889
] 

Jon Schneider commented on IVYDE-208:
-------------------------------------

Ivica,

Thanks for the feedback.

- I developed this on 3.4 and have been using it in RAD 7.5.3.  You do need to install Zest
separately on most 3.4 installations I believe.
- I changed the text of the classpath containers in the dialog box per your suggestion.
- I moved the call to org.eclipse.ui.ISharedImages, thinking that maybe somehow the view class
was getting loaded before a workbench was available from PlatformUI?  Honestly, I'm not the
most experienced Eclipse plugin developer.  Please let me know if that works for you.  I see
the images here without trouble on Eclipse 3.4, 3.5, and RAD 7.5.3.

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


Mime
View raw message