[
https://issues.apache.org/jira/browse/IVYDE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750907#action_12750907
]
Phillip Webb commented on IVYDE-187:
------------------------------------
I think the problem was that I do not assign version numbers to projects until
the build process. I think that most of my ivy files had ${version} variables.
I also seem to recall that this related to transitive dependencies in the
workspace and using latest.integration as the dependency version. To be honest
this was a little while ago and I have forgotten the exact cause of the
problem, but I do remember stepping though the plug-in and this was the only
option that I could find to fix my issue.
I also think that it is quite a useful addition. |My guess is that it is a
fairly common use case to only have one project inside eclipse for a given
dependency. Not having to worry about version numbers makes life easier,
especially as a failure on the resolve is sometimes hard to track down.
> 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.
