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] Issue Comment Edited: (IVYDE-208) Ivy Resolve Visualizer
Date Thu, 01 Oct 2009 12:33:23 GMT

    [ 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 5:31 AM:
--------------------------------------------------------------

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



      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


  
> 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: screenshot-1.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