[
https://issues.apache.org/jira/browse/IVYDE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761833#action_12761833
]
Ivica Loncar commented on IVYDE-208:
------------------------------------
Nice work. I was prepared to do something similar, but now there is no need to
re-invent the wheel. Thanks. ;-)
Couple of suggestions/requests:
- I would like this feature to run on eclipse 3.4.x since all of our clients
that use ivy also use Rational development tools
- Users should be able to choose ivy configuration that should be visualized.
When users add multiple ivy containers to the classpath they see classpath
container named like: "ivy.xml [conf1]" but in the visualizer there are
multiple "Project name (ivy.xml)" entries. I think the label should be "Project
name (ivy.xml/conf1)".
There are "Previous view" and "Go forward one plugin" icons in the view toolbar
but I can't see the icons and I do have org.eclipse.ui enabled in the target
platform.
Do you know why these shared images are not loading? What could be missing?
> 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, 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.
