Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 48765200C80 for ; Thu, 25 May 2017 12:16:49 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 47133160BCA; Thu, 25 May 2017 10:16:49 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8DCD5160BC7 for ; Thu, 25 May 2017 12:16:48 +0200 (CEST) Received: (qmail 72082 invoked by uid 500); 25 May 2017 10:16:47 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 72060 invoked by uid 99); 25 May 2017 10:16:47 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 May 2017 10:16:47 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id F18BCC0027 for ; Thu, 25 May 2017 10:16:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.951 X-Spam-Level: * X-Spam-Status: No, score=1.951 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id w9VZDWsx6exK for ; Thu, 25 May 2017 10:16:44 +0000 (UTC) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id B65F75F477 for ; Thu, 25 May 2017 10:16:44 +0000 (UTC) Received: from [192.168.1.15] (unknown [82.227.128.48]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 9D092509BB for ; Thu, 25 May 2017 06:16:37 -0400 (EDT) From: =?utf-8?Q?Nicolas_Lalev=C3=A9e?= Content-Type: multipart/alternative; boundary="Apple-Mail=_B1F995C4-CB95-4777-BAF4-D7D90D09D09A" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Versioning scheme in Ivy Date: Thu, 25 May 2017 12:16:36 +0200 References: To: Ant Developers List In-Reply-To: Message-Id: <82ABC12D-7B3F-47CA-8DFC-AD160793DB24@hibnet.org> X-Mailer: Apple Mail (2.3273) archived-at: Thu, 25 May 2017 10:16:49 -0000 --Apple-Mail=_B1F995C4-CB95-4777-BAF4-D7D90D09D09A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 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-match= ers.html = > Le 24 mai 2017 =C3=A0 10:22, Gintautas Grigelionis = a =C3=A9crit : >=20 > Sorry, I meant to ask what may happen if special characters from range > specification are used randomly in a version string? >=20 > Gintas >=20 > 2017-05-24 10:15 GMT+02:00 Gintautas Grigelionis = : >=20 >> 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? >>=20 >> Gintas >>=20 --Apple-Mail=_B1F995C4-CB95-4777-BAF4-D7D90D09D09A--