[
https://issues.apache.org/jira/browse/IVYDE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762322#action_12762322
]
Jon Schneider edited comment on IVYDE-208 at 10/5/09 12:32 PM:
---------------------------------------------------------------
Added configuration conflict detection algorithm and highlighting. See
screenshot-6 for a visual overview of the additions. I also attached an
example ivy.xml file that has conflicts so you can see the effect yourself.
Concerning wide graphs, I agree. My graphs sometimes get very wide as well. I
wonder if I can reorient the nodes on a 45 degree angle (probably not)...
Maybe a newline between org and name would help narrow the graph somewhat.
I'll play around with it. This phenomenon led me to try to make the thumbnail
previewer a little shorter and wider as well to save on screen real estate. I
fiddled with it for a half hour and couldn't figure out a way to accomplish it.
Concerning files that are not associated with containers, I heard the same
question from developers here. I am a little uncomfortable moving forward on
this until I hear feedback from Nicolas, because I am already somewhat abusing
the IvyResolveJob (at least using it in a way it wasn't intended for). We may
have to do a little refactoring in other parts of the plugin to expose the
resolve capability outside of the Job if we are going to pursue this. I
totally agree that it is an important feature, though.
was (Author: jkschneider):
Added configuration conflict detection algorithm and highlighting. See
screenshot-6 for a visual overview of the additions. I also attached an
example ivy.xml file that has conflicts so you can see the effect yourself.
Concerning wide graphs, I agree. My graphs sometimes get very wide as well. I
wonder if I can reorient the nodes on a 45 degree angle (probably not)...
Maybe a newline between org and name would help narrow the graph somewhat.
I'll play around with it.
Concerning files that are not associated with containers, I heard the same
question from developers here. I am a little uncomfortable moving forward on
this until I hear feedback from Nicolas, because I am already somewhat abusing
the IvyResolveJob (at least using it in a way it wasn't intended for). We may
have to do a little refactoring in other parts of the plugin to expose the
resolve capability outside of the Job if we are going to pursue this. I
totally agree that it is an important feature, though.
> 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, 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.
-
You can reply to this email to add a comment to the issue online.
