You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Nicolas Lalevée (JIRA)" <ji...@apache.org> on 2010/08/25 12:23:15 UTC

[jira] Resolved: (IVYDE-234) Add branch comparison to workspace resolver

     [ https://issues.apache.org/jira/browse/IVYDE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Lalevée resolved IVYDE-234.
-----------------------------------

         Assignee: Nicolas Lalevée
    Fix Version/s: 2.2.0
       Resolution: Fixed

Patch applied, thanks Jeffrey !

> Add branch comparison to workspace resolver
> -------------------------------------------
>
>                 Key: IVYDE-234
>                 URL: https://issues.apache.org/jira/browse/IVYDE-234
>             Project: IvyDE
>          Issue Type: New Feature
>          Components: workspace resolver
>    Affects Versions: 2.0.0.final
>            Reporter: Jeffrey M. Metcalf
>            Assignee: Nicolas Lalevée
>            Priority: Minor
>             Fix For: 2.2.0
>
>         Attachments: ivyde-234.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Currently IvyDE uses the org, module, (and revision by default) when resolving workspace dependencies.  I propose adding branch as an optional attribute to be matched in the workspace dependency code.  For consistency with the current workspace dependency configuration, I would add an option to ignore branch in the comparison similar to the option for revision.  As with revision, the default would be unchecked.  This means that the default would be to compare branch attributes when identifying project dependencies, which helps guarantee the correct and most appropriate dependency match.  The addition of the branch attribute in the comparison helps in the case where more than one project exists on the same module in the Eclipse workspace and another project defines a latest.status dependency on that module.  The current revision comparison code fails to detect the difference between the dependent workspace projects.  Therefore by specifying a value for branch in the dependency and module descriptor, a correct match is found.

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