You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by "Gilles Scokart (JIRA)" <ji...@apache.org> on 2007/01/15 10:48:27 UTC
[jira] Created: (IVY-390) java.lang.IllegalArgumentException:
Invalid uri when working with version ranges
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
Reporter: Gilles Scokart
From the user mailing list :
On 1/12/07, Cecile <ru...@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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (IVY-390) java.lang.IllegalArgumentException:
Invalid uri when working with version ranges
Posted by "Gilles Scokart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gilles Scokart resolved IVY-390.
--------------------------------
Resolution: Cannot Reproduce
Please reopen if required.
> 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
> Reporter: Gilles Scokart
> Fix For: 2.0
>
> Attachments: IVY-390.zip
>
>
> From the user mailing list :
> On 1/12/07, Cecile <ru...@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.
[jira] Updated: (IVY-390) java.lang.IllegalArgumentException:
Invalid uri when working with version ranges
Posted by "Gregoire Henry (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregoire Henry updated IVY-390:
-------------------------------
Attachment: IVY-390.zip
test for IVY-390 issue
> 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
> Reporter: Gilles Scokart
> Fix For: 1.5
>
> Attachments: IVY-390.zip
>
>
> From the user mailing list :
> On 1/12/07, Cecile <ru...@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.
[jira] Assigned: (IVY-390) java.lang.IllegalArgumentException:
Invalid uri when working with version ranges
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ 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 <ru...@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.
[jira] Commented: (IVY-390) java.lang.IllegalArgumentException:
Invalid uri when working with version ranges
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475171 ]
Maarten Coene commented on IVY-390:
-----------------------------------
I've added a junit test for this issue to URLResolverTest, but I was unable to reproduce the problem.
> 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
> Reporter: Gilles Scokart
> Fix For: 1.5
>
>
> From the user mailing list :
> On 1/12/07, Cecile <ru...@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.
[jira] Updated: (IVY-390) java.lang.IllegalArgumentException:
Invalid uri when working with version ranges
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xavier Hanin updated IVY-390:
-----------------------------
Fix Version/s: 1.5
> 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
> Reporter: Gilles Scokart
> Fix For: 1.5
>
>
> From the user mailing list :
> On 1/12/07, Cecile <ru...@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.
[jira] Updated: (IVY-390) java.lang.IllegalArgumentException:
Invalid uri when working with version ranges
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene updated IVY-390:
------------------------------
Affects Version/s: 2.0.0-alpha-2
> 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
> Fix For: 2.0
>
> Attachments: IVY-390.zip
>
>
> From the user mailing list :
> On 1/12/07, Cecile <ru...@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.
[jira] Commented: (IVY-390) java.lang.IllegalArgumentException:
Invalid uri when working with version ranges
Posted by "Robert Macaulay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494127 ]
Robert Macaulay commented on IVY-390:
-------------------------------------
Having a similar problem as well
{noformat}
[ivy-retrieve] tried http://server:9090/ivy-repo/extern/wstx-asl/[revision]/ivy.xml
[ivy-retrieve] tried http://server:9090/ivy-repo/extern/wstx-asl/[revision]/jar/wstx-asl.jar
[ivy-retrieve] 3textern-repository: no ivy file nor artifact found for [ extern | wstx-asl | [3.0.1,) ]
{noformat}
On the web server,
{noformat}
http://server:9090/ivy-repo/extern/wstx-asl/
{noformat}
directory has a 3.2.0 directory under it.
Our ivy resolver element has this for the pattern
{noformat}
http://server:9090/ivy-repo/[organisation]/[module]/[revision]/ivy.xml
{noformat}
> 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
> Reporter: Gilles Scokart
> Fix For: 2.0
>
> Attachments: IVY-390.zip
>
>
> From the user mailing list :
> On 1/12/07, Cecile <ru...@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.
[jira] Commented: (IVY-390) java.lang.IllegalArgumentException:
Invalid uri when working with version ranges
Posted by "Gregoire Henry (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481532 ]
Gregoire Henry commented on IVY-390:
------------------------------------
I've added a test file to this issue showing how I produce this bug .
I also try to reproduce this issue with other resolver (filesystem) but without succes ..
HTH
Greg
> 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
> Reporter: Gilles Scokart
> Fix For: 1.5
>
>
> From the user mailing list :
> On 1/12/07, Cecile <ru...@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.
[jira] Reopened: (IVY-390) java.lang.IllegalArgumentException:
Invalid uri when working with version ranges
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene reopened IVY-390:
-------------------------------
I cannot resolve following dependency when httpclient is in my classpath:
<dependency org="commons-lang" name="commons-lang" rev="[1.0,3.0[" />
I get the following error:
{code}
[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:retrieve] :: UNRESOLVED DEPENDENCIES ::
[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:retrieve] :: [ commons-lang | commons-lang | [1.0,3.0[ ]: Invalid
uri 'http://repo1.maven.org/maven2/commons-lang/commons-lang/[1.0,3.0[/commons-l
ang-[1.0,3.0[.pom': escaped absolute path not valid
[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
{code}
I don't have any stacktrace.
> 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
> Reporter: Gilles Scokart
> Fix For: 2.0
>
> Attachments: IVY-390.zip
>
>
> From the user mailing list :
> On 1/12/07, Cecile <ru...@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.
[jira] Resolved: (IVY-390) java.lang.IllegalArgumentException:
Invalid uri when working with version ranges
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene resolved IVY-390.
-------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.0)
2.0.0-beta-1
Should be ok now
> 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.0-beta-1
>
> Attachments: IVY-390.zip
>
>
> From the user mailing list :
> On 1/12/07, Cecile <ru...@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.
[jira] Commented: (IVY-390) java.lang.IllegalArgumentException:
Invalid uri when working with version ranges
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494671 ]
Xavier Hanin commented on IVY-390:
----------------------------------
I'm trying to reproduce the issue, and I don't manage to with Ivy 2.0.0 alpha 1, even with your test case, Gregoire.
So this may be related to the environment... could you give more detail on your web server? And maybe also attach a debug log?
> 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
> Reporter: Gilles Scokart
> Fix For: 2.0
>
> Attachments: IVY-390.zip
>
>
> From the user mailing list :
> On 1/12/07, Cecile <ru...@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.