You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Matt Goldspink (JIRA)" <ji...@apache.org> on 2009/06/03 11:00:07 UTC

[jira] Commented: (IVYDE-153) Better support the resolve in workspace feature

    [ https://issues.apache.org/jira/browse/IVYDE-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715873#action_12715873 ] 

Matt Goldspink commented on IVYDE-153:
--------------------------------------

Just thought I'd update and say I've been using this for over month now and had no issues. It's been working great for us. Thanks

> Better support the resolve in workspace feature
> -----------------------------------------------
>
>                 Key: IVYDE-153
>                 URL: https://issues.apache.org/jira/browse/IVYDE-153
>             Project: IvyDE
>          Issue Type: Improvement
>    Affects Versions: 2.0.0.beta1
>            Reporter: Nicolas Lalevée
>            Assignee: Nicolas Lalevée
>             Fix For: 2.0.0.final
>
>         Attachments: IVYDE-153-r736034.patch
>
>
> Today the "resolve in workspace" feature is quite a work around: the resolve process run against the real artifacts in the real repositories, and only after that the resolved artifacts are maybe replaced by the project.
> Drawbacks:
> * the resolve can fail if the artifact is not build but the project exist
> * we have no control of when a project is included or not
> So what we need here is a specific implementation of Ivy's DependencyResolver managed by IvyDE.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.