[
https://issues.apache.org/jira/browse/IVYDE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761192#action_12761192
]
Jon Schneider edited comment on IVYDE-208 at 10/1/09 12:54 PM:
---------------------------------------------------------------
So far I have built this visualizer with the following features:
1. Automatic highlights of:
- Shortest path to root
- All paths to root
- All callers
- All dependencies
- Other revisions
2. Filtering options:
- Hide evictions
- Limit depth (only show up to the n-th level transitive dependency)
- Hide selection
3. Focusing:
- Focus on an ivy classpath container
- Focus on a selection
4. Zooming
5. Print screen
6. Searching
7. History
8. Hide/Show All nodes (not sure if this is really a useful feature or not)
Scrubbing the code a bit -- patch coming soon.
was (Author: jkschneider):
So far I have built this visualizer with the following features:
1. Automatic highlights of:
- Shortest path to root
- All paths to root
- All callers
- All dependencies
- Other revisions
2. Filtering options:
- Hide evictions
- Limit depth (only show up to the n-th level transitive dependency)
- Hide selection
3. Focusing:
- Focus on an ivy classpath container
- Focus on a selection
4. Zooming
5. Print screen
6. Searching
7. History
Scrubbing the code a bit -- patch coming soon.
> 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,
> screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.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.
