ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Goldspink (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVYDE-187) Allow workspace resolver to skip version matcher
Date Thu, 10 Sep 2009 10:24:57 GMT

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

Matt Goldspink commented on IVYDE-187:
--------------------------------------

I understand the concern about having 2 projects in your workspace for different revisions
of the same project, but could that not also be solved with a dialog box from IvyDE when hits
this case. It should only pop that up if there is no version match and multiple projects are
found. I know popping up dailog boxes isn't everyone's cup of tea, so maybe the way to deal
with revisions in the workspace resolver is to offer 3 choices when dealing with this situation:


1) fail fast
2) open a selection dialog box with the choices
3) always choose the first match (not sure if this is the best approach, but at least it will
keep things working in the workspace and people don't have to be hassled with a dialog box)





> Allow workspace resolver to skip version matcher
> ------------------------------------------------
>
>                 Key: IVYDE-187
>                 URL: https://issues.apache.org/jira/browse/IVYDE-187
>             Project: IvyDE
>          Issue Type: Improvement
>          Components: workspace resolver
>    Affects Versions: 2.0.0.final
>            Reporter: Phillip Webb
>         Attachments: ivyde-workspaceignoreversion.patch
>
>
> The workspace resolver version matcher sometimes gets in the way.  I would like to suggest
an option that will allow a workspace project to be used when the organization and module
ID match, regardless of the version.  
> The DocComment on WorkspaceResolver seems to imply that this was the original intent:
>   * Since the resolver is not aware which module revision a project is publishing, it
optimistically
>   * matches any revision of the module.

-- 
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