Return-Path: 
 <ivy-user-return-279-apmail-incubator-ivy-user-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org
Received: (qmail 28403 invoked from network); 15 Jan 2007 10:48:22 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 15 Jan 2007 10:48:22 -0000
Received: (qmail 79187 invoked by uid 500); 15 Jan 2007 10:48:29 -0000
Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org
Received: (qmail 79171 invoked by uid 500); 15 Jan 2007 10:48:28 -0000
Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@incubator.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@incubator.apache.org>
List-Post: <mailto:ivy-user@incubator.apache.org>
List-Id: <ivy-user.incubator.apache.org>
Reply-To: ivy-user@incubator.apache.org
Delivered-To: mailing list ivy-user@incubator.apache.org
Received: (qmail 79162 invoked by uid 99); 15 Jan 2007 10:48:28 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jan 2007 02:48:28 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of gscokart@gmail.com designates
 66.249.92.174 as permitted sender)
Received: from [66.249.92.174] (HELO ug-out-1314.google.com) (66.249.92.174)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jan 2007 02:48:18 -0800
Received: by ug-out-1314.google.com with SMTP id y2so1507916uge
        for <ivy-user@incubator.apache.org>;
 Mon, 15 Jan 2007 02:47:57 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:from:to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:in-reply-to:x-mimeole:thread-index;
        b=PUM+9QKS5alPl9Ns1cjtLM17cZc2QVR0quc7R0uXZQ3/les7uXHw8BzIX/CUe7asIQQmTmwJKr/QdyB7ED6VY9eHYve7ug3IE3aZpBFQd0C35dSmaix78AZFvY+KsNoM8TeOeUrKv1dKwvrk4KQIjlSUt6qkbWLEEvXZMvVozBg=
Received: by 10.67.106.3 with SMTP id i3mr5189029ugm.1168858077367;
        Mon, 15 Jan 2007 02:47:57 -0800 (PST)
Received: from cer1352 ( [195.122.110.8])
        by mx.google.com with ESMTP id m1sm5396458ugc.2007.01.15.02.47.56;
        Mon, 15 Jan 2007 02:47:56 -0800 (PST)
From: "Gilles Scokart" <gscokart@gmail.com>
To: <ivy-user@incubator.apache.org>
Subject: RE: (ivy 1.4) Problem using version ranges
Date: Mon, 15 Jan 2007 11:47:55 +0100
Message-ID: <004401c73892$9d88aff0$3020a8c0@isabelteam.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <1CCEA1ACF736B749B6FEE53168A6BF0001E73301@server1e>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: Acc4kUkHUDBzolhPRoKjovGfIwJVzQAAU1wg
X-Virus-Checked: Checked by ClamAV on apache.org

Done : https://issues.apache.org/jira/browse/IVY-390

Gilles 

> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com] 
> Sent: Monday, January 15, 2007 11:38 AM
> To: ivy-user@incubator.apache.org
> Subject: Re: (ivy 1.4) Problem using version ranges
> 
> On 1/15/07, Gilles Scokart <gscokart@gmail.com> wrote:
> >
> > Is there already a jira issue for that?  The work around is simple, 
> > but the bug might popup for any user who use version ranges.
> 
> 
> I agree, one should open an issue for that.
> 
> Xavier
> 
> Gilles
> >
> > > -----Original Message-----
> > > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > > Sent: Friday, January 12, 2007 8:03 AM
> > > To: ivy-user@incubator.apache.org
> > > Subject: Re: (ivy 1.4) Problem using version ranges
> > >
> > > On 1/12/07, Cecile <rubycoder@gmail.com> wrote:
> > > >
> > > > I am using revision ranges like this:
> > > >
> > > > <dependency org="ops4j" name="org.ops4j.pax.wicket" 
> rev="[0.3,1.0]"
> > > > conf="compile,runtime->default">
> > > >     <artifact name="service" type="jar"/> </dependency>
> > > >
> > > > However, it gives me the error:
> > > >
> > > > [ivy:retrieve]          ::          UNRESOLVED DEPENDENCIES
> > >         ::
> > > > [ivy:retrieve]
> > > ::::::::::::::::::::::::::::::::::::::::::::::
> > > > [ivy:retrieve]          :: [ ops4j | org.ops4j.pax.wicket |
> > > [0.3,1.0]
> > > > ]: several problems occured while resolving depend
> > > > ency: [ ops4j | org.ops4j.pax.wicket | [0.3,1.0] ]
> > > {runtime=[default],
> > > > compile=[default]}:
> > > > [ivy:retrieve] java.lang.IllegalArgumentException: Invalid uri
> > > > 'http://localhost:8084/artifacts/ivy-repo/ops4j/org.ops4j
> > > > .pax.wicket/ivys/ivy-[0.3,1.0].xml': escaped absolute 
> path not valid
> > > >
> > > > I thought ivy 1.4 supports revision ranges ?
> > >
> > >
> > > Yes it does, but since it's a recent feature it can still
> > > cause problem in some cases. Here the problem is that Ivy
> > > always try to see if the asked revision is not an exact
> > > revision, but it fails because the URL is not valid at all
> > > with these characters. The solution is to set the property "
> > > ivy.default.always.check.exact.revision" to false, then Ivy
> > > will avoid testing what you ask as an exact revision first,
> > > and hopefully it will fix your problem.
> > >
> > > Xavier
> > >
> > >
> > > Thanks
> > > >
> > >
> >
> >
>