Re: Versioning scheme in Ivy

Sorry for a roundabout way of getting to the point, but wouldn't the characters used in matchers be treated in a special way, thus restricting their use in version strings? On a related theme, should Ivy support semver ranges [1]? (that would include >, <, >=, <=, =, ||, &, !, and shorthands [2] *

Re: Versioning scheme in Ivy

Almost everything in Ivy is configurable, like the version matchers [1]. Ivy provide some sane default, but if some has a weird use case, he will be able to tweak thing to make it work. Nicolas [1] https://ant.apache.org/ivy/history/latest-milestone/settings/version-matchers.html

Re: Versioning scheme in Ivy

Sorry, I meant to ask what may happen if special characters from range specification are used randomly in a version string? Gintas 2017-05-24 10:15 GMT+02:00 Gintautas Grigelionis : > I was thinking about the discussion which touched upon restricted > characters in version strings. While Ivy doe

Versioning scheme in Ivy

I was thinking about the discussion which touched upon restricted characters in version strings. While Ivy does not place any restrictions on those strings, Ivy does support versions ranges as specified by OSGi. So, what happens if version range is used as a version string? Gintas