incubator-ivy-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Coene (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (IVY-390) java.lang.IllegalArgumentException: Invalid uri when working with version ranges
Date Fri, 21 Sep 2007 12:59:50 GMT

     [ https://issues.apache.org/jira/browse/IVY-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Maarten Coene reassigned IVY-390:
---------------------------------

    Assignee: Maarten Coene

> java.lang.IllegalArgumentException: Invalid uri when working with version ranges
> --------------------------------------------------------------------------------
>
>                 Key: IVY-390
>                 URL: https://issues.apache.org/jira/browse/IVY-390
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.4.1, 2.0.0-alpha-2
>            Reporter: Gilles Scokart
>            Assignee: Maarten Coene
>             Fix For: 2.0
>
>         Attachments: IVY-390.zip
>
>
> From the user mailing list :
> 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

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message