Done : https://issues.apache.org/jira/browse/IVY-390
Gilles > -----Original Message----- > From: Xavier Hanin [mailto:[EMAIL PROTECTED] > Sent: Monday, January 15, 2007 11:38 AM > To: [email protected] > Subject: Re: (ivy 1.4) Problem using version ranges > > On 1/15/07, Gilles Scokart <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED] > > > Sent: Friday, January 12, 2007 8:03 AM > > > To: [email protected] > > > Subject: Re: (ivy 1.4) Problem using version ranges > > > > > > On 1/12/07, Cecile <[EMAIL PROTECTED]> 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 > > > > > > > > > > > >
