[
https://issues.apache.org/jira/browse/IVYDE-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée resolved IVYDE-195.
-----------------------------------
Resolution: Fixed
Assignee: Nicolas Lalevée
So I integrated with few cosmetic code change: formatting, created an
revdepexplorer package.
I had only one worry: IvyClasspathUtil#toIvyFile() will only properly work on
ivy file in the workspace. It is possible to have some absolute path here. I
don't think this is a primery use case and the code won't break (the Eclipse
API will see them as read only as far as I could see). So I just put a TODO.
And I have created a page about the new view in the doc. I would be nice if you
can take time to write some paragraphs about it, how to use it, present some
use case.
thanks a lot for your patch Jon !
> "Ivy Dependency Explorer" View for synchronizing revisions across multiple
> projects in a workspace
> --------------------------------------------------------------------------------------------------
>
> Key: IVYDE-195
> URL: https://issues.apache.org/jira/browse/IVYDE-195
> Project: IvyDE
> Issue Type: New Feature
> Reporter: Jon Schneider
> Assignee: Nicolas Lalevée
> Fix For: 2.1.0
>
> Attachments: ivyde-195(3).patch, ivyde-195(3).patch,
> new-project-menu-item.jpg, projects-represented-in-explorer.jpg, synced.gif
>
>
> When working with multiple projects in a workspace that represent the whole
> or part of a larger application, I often want to bring the revisions of
> dependencies up to a single new revision all at the same time
> (notwithstanding the wonderful eviction mechanism inherent to Ivy).
> Other times it is instructive just to see what dependencies are being
> utilized by projects in the workspace by revision without having to dig into
> each project and look at each individual module descriptor.
> I am introducing the Ivy Dependency explorer that turns the tree upside-down,
> exploring the workspace by organization, module, and revision and providing a
> mechanism to synchronize revisions across projects/classpath containers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
