Return-Path: 
 <ivy-user-return-7833-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: (qmail 91997 invoked from network); 13 Apr 2011 11:24:38 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 13 Apr 2011 11:24:38 -0000
Received: (qmail 95899 invoked by uid 500); 13 Apr 2011 11:24:38 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 95860 invoked by uid 500); 13 Apr 2011 11:24:37 -0000
Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@ant.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@ant.apache.org>
List-Post: <mailto:ivy-user@ant.apache.org>
List-Id: <ivy-user.ant.apache.org>
Reply-To: ivy-user@ant.apache.org
Delivered-To: mailing list ivy-user@ant.apache.org
Received: (qmail 95851 invoked by uid 99); 13 Apr 2011 11:24:37 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Apr 2011 11:24:37 +0000
X-ASF-Spam-Status: No, hits=2.2 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received: from [74.125.83.173] (HELO mail-pv0-f173.google.com) (74.125.83.173)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Apr 2011 11:24:30 +0000
Received: by pvg3 with SMTP id 3so226301pvg.4
        for <ivy-user@ant.apache.org>; Wed, 13 Apr 2011 04:24:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=steelezone.net; s=google;
        h=domainkey-signature:mime-version:in-reply-to:references:date
         :message-id:subject:from:to:content-type;
        bh=dEjKWZj3vtwXtDLBAsloEOcUOCFP1lVozQpcdIbGwxU=;
        b=EdNevQ86keaflN08XD/ALFYukczXmnGNE7Y7rM4bON33z1yhh7ahdwkxobcDi/Q76c
         RptHBT5OcNA6mtZVpVTL5sDFR7Iyv/Mpp2AsiJiDzCGNyBYHTNMXF3uvU42mof1hLysF
         Hx1Kf92+wzpHrVVUzMlVmURQyjfXcfWsoQDQc=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=steelezone.net; s=google;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=L1ffjcczmSj7NMX2MxLb0q7h68G3YGSKvnZ4OLH25XeGbPqBUw52nGSO0y6ORjlrUZ
         WdtQjDBGN7MbaCJCGEMbIPPmRKztR20SQilrav1r9d2pXKJxmc8kiKKJs5TAYWMaD5wx
         NIiIQv40LAYtHcvaFh3cNWjX95Lsp2kL7y1tM=
MIME-Version: 1.0
Received: by 10.143.24.40 with SMTP id b40mr7497704wfj.275.1302693848234; Wed,
 13 Apr 2011 04:24:08 -0700 (PDT)
Received: by 10.68.65.170 with HTTP; Wed, 13 Apr 2011 04:24:08 -0700 (PDT)
In-Reply-To: <BANLkTikMY71KMM97SkB3BGcsO53uckvEBA@mail.gmail.com>
References: <BANLkTikMY71KMM97SkB3BGcsO53uckvEBA@mail.gmail.com>
Date: Wed, 13 Apr 2011 07:24:08 -0400
Message-ID: <BANLkTi=yRPSyvx_Ly1LtA5M2ubLVCV0SJQ@mail.gmail.com>
Subject: Re: Using dynamic revision but restrict status?
From: "Steele, Richard" <rich@steelezone.net>
To: ivy-user@ant.apache.org
Content-Type: multipart/alternative; boundary=001636e0b6e213393304a0cb0c67
X-Virus-Checked: Checked by ClamAV on apache.org

--001636e0b6e213393304a0cb0c67
Content-Type: text/plain; charset=ISO-8859-1

Bump.

This isn't something anyone else has had to deal with?  Or am I missing
something completely obvious?  Is the answer as simple as "don't ever use
dynamic revisions?"  If so, then what good are they?

If this isn't currently possible, would an enhancement request be
worthwhile?  I envision allowing a dependency along the lines of

<dependency org="com.example" name="foo" rev="[1.0,1.1[" status="milestone"
/>

to mean a revision in the specified range with a status of milestone or
greater.  This would also allow for something like

<dependency org="com.example" name="foo" rev="latest" status="milestone" />

as a synonym for the current "latest.*status*" mechanism.

Thoughts?  Please?

Rich

On Thu, Apr 7, 2011 at 3:13 PM, Steele, Richard <rich@steelezone.net> wrote:

> Is it possible for me to declare a dependency using a dynamic revision
> while restricting the status of the retrieved artifact?  For example, I want
> to define a version range, something like "[1.0,1.1[", but I don't want
> artifacts with a status of integration, only milestone or release.  So I
> want version 1.0.5 if it has a status of "release" even if there's a version
> 1.0.6 with a status of "integration."
>
> I know about latest.*status*, but that's not really what I want: I need to
> define an upper and lower limit on the revision.
>
> Thanks,
> Rich
>

--001636e0b6e213393304a0cb0c67--