[
https://issues.apache.org/jira/browse/IVY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289274#comment-17289274
]
Gintas Grigelionis commented on IVY-1614:
-----------------------------------------
I believe that some examples in the documentation cover Maven version ranges,
but not completely (Maven 3.5+ has introduced lists of ranges). What is
confusing is a lack of clarity of what is supported or not (as witnessed by
[this discussion|https://github.com/sbt/sbt/issues/2954]).
> 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)
