[
https://issues.apache.org/jira/browse/IVYDE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750991#action_12750991
]
Nicolas Lalevée commented on IVYDE-187:
---------------------------------------
Effectively with some ${version} it doesn't work.
And about use cases, sometimes I have to open an old version of a project
(usualy a bug fix in the branch), so this can be quite error prone or painfull
to make IvyDE ignore project's versions, as the new option you suggest is
global to the workspace. So I think that this option might be harmful, but you
use case is perfectly valid. I think I will probably integrate your patch and
add a warning about its use in the global preference page.
Note that as a workaround, Ivy can set the published version: see the use of
the attribute pubrevision in the
[deliver|http://ant.apache.org/ivy/history/latest-milestone/use/deliver.html]
ant task
But you might then hit IVYDE-186
> 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.
