[
https://issues.apache.org/jira/browse/IVY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289259#comment-17289259
]
Björn Kautler commented on IVY-1614:
------------------------------------
Ah, you are completely right.
I think my problem was, that we use Gradle as build tool and it ordered the
versions the same and thus didn't find a match.
I guess I assumed it is a problem of the "wrong" version range, but I don't
remember exactly what I thought back then.
Maybe then [https://ant.apache.org/ivy/history/2.5.0/ivyfile/dependency.html]
should mention that also Maven version ranges are accepted? :)
> Ivy needs to translate Maven version ranges
> -------------------------------------------
>
> Key: IVY-1614
> URL: https://issues.apache.org/jira/browse/IVY-1614
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Björn Kautler
> Assignee: Jaikiran Pai
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Syntax for version ranges is differing between Maven and Ivy.
> If a dependency is installed from a Maven repository and installed to an Ivy
> repository using the install task, the version ranges need to be translated.
> For example if you install from Maven Central to some Ivy repository the
> library {{org.eclipse.emf:ecore:2.3.0-v200706262000}}, then you end up with
> this in your Ivy file:
> {code:xml}
> <dependency org="org.eclipse.emf" name="common" rev="[2.3.0,3.0.0)"
> force="true" conf="compile->compile(*),master(*);runtime->runtime(*)"/>
> {code}
> while in Ivy syntax this should be
> {code:xml}
> <dependency org="org.eclipse.emf" name="common" rev="[2.3.0,3.0.0["
> force="true" conf="compile->compile(*),master(*);runtime->runtime(*)"/>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
