ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Turner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVYDE-234) Add branch comparison to workspace resolver
Date Fri, 02 Jul 2010 08:31:52 GMT

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

Ben Turner commented on IVYDE-234:
----------------------------------

Reading through this, not sure if it addresses the case I am struggling with. Similar deal,
where code on trunk or a release branch is marked as "latest.integration". However, I have
a different workspace per branch, so avoid the problems you were having. The problem I have
is on trunk, the replacement's work. But on trunk, it doesn't identify the modules as related
and does no substitution.

I had also noted we don't publish our artifacts with a "branch" tag - we use version number
alone to lock down dependencies (e.g. 17.0-+ or HEAD-+). This might also be required I guess.


> 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
>            Priority: Minor
>         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.


Mime
View raw message