[
https://issues.apache.org/jira/browse/IVYDE-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée resolved IVYDE-225.
-----------------------------------
Resolution: Duplicate
I think you are hitting the same issue I have: IVYDE-212
> Workspace resolver does not force transitive workspace dependencies
> -------------------------------------------------------------------
>
> Key: IVYDE-225
> URL: https://issues.apache.org/jira/browse/IVYDE-225
> Project: IvyDE
> Issue Type: Bug
> Components: workspace resolver
> Affects Versions: 2.0.0.final
> Reporter: Jeffrey Sinclair
> Priority: Minor
>
> Take the following use-case (all projects are in the workspace):
> * Project A -> Project B -> Project C.
> * Project A -> Project C.
>
> Now lets assume that Project A has resolve in workspace turned on. The
> expectation is that Project C should be resolved from the workspace. However
> if Project B does not have resolve in workspace enabled and can resolve
> Project C using a different resolver, then there is a chance that Project A
> will use B's resolved location of C instead of from the workspace.
> My current thinking is that the workspace resolver should behave _as-if_ a
> <modules> section had been added to Project A's ivysettings.xml file
> specifying that the workspace resolver should be used for Project C if
> Project C exists in the workspace. If this view is taken then this is a bug
> in the workspace resolver.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
