ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <j...@apache.org>
Subject [jira] Commented: (IVY-1134) Incremental Resolve
Date Tue, 06 Oct 2009 18:10:31 GMT

    [ https://issues.apache.org/jira/browse/IVY-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762719#action_12762719
] 

Nicolas Lalevée commented on IVY-1134:
--------------------------------------

I don't have any opinion yet on that subject, I didn't had time to look into the Ivy Resolve
Visualizer (at least it looks amazing from the screenshots :) ).
But this kind of design, brainstorming discussion is usually done on the dev@ant.apache.org
mailing list. So you will get most developers attention and opinions.

> Incremental Resolve
> -------------------
>
>                 Key: IVY-1134
>                 URL: https://issues.apache.org/jira/browse/IVY-1134
>             Project: Ivy
>          Issue Type: Wish
>          Components: Ant, Core
>            Reporter: Jon Schneider
>            Priority: Minor
>
> I am trying to integrate an Eclipse Zest (GEF) Ivy resolve visualizer into IvyDE to help
our developers visualize the eviction process and to see how transitive dependencies were
brought into the classpath.  What started out as a visualizer is now being considered as a
type of editor as well.  Of course, if we edit a node visually (whether it be changing a version,
excluding a node, toggling the transitive attribute, etc.), we have to perform a resolve against
the whole ivy file associated with that visualization (which may not be quick).  I want to
get some opinions on an incremental resolve feature, which would somehow compare the cached
resolve file with the changing ivy file and resolve just the delta.
> So just brainstorming, here are my thoughts:
> - persist a copy (in the cache) of relevant pieces of the ivy file whenever a resolve
is performed so that the file can be compared on a subsequent resolve.
> - we can pretty easily resolve just the particular dependencies that change, and the
results could only have two impacts on the rest of the tree stemming from:
> ## evictions
> ## exclusions
> WDYT?

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