Uploaded image for project: 'IvyDE'
  1. IvyDE
  2. IVYDE-225

Workspace resolver does not force transitive workspace dependencies

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 2.0.0.final
    • Fix Version/s: None
    • Component/s: workspace resolver
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jeffrey.sinclair Jeffrey Sinclair
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: