Yup, that was it, DOH! Thanks for pointing that out.
Anyway, I removed it, did a fresh checkout and retrieve and building
jars goes fine. Should the unit tests work out of the box or is extra
setup required? They all seem to fail for me. Would be nice if the
test-report task generated an HTML version as this usually gives a much
nicer overview of what happened with the tests, but maybe that's just my
opinion...
Maarten Coene wrote:
Are you sure you don't have an older version of ivy in the lib directory of
your Ant installation?
regards,
Maarten
----- Original Message ----
From: Xavier Hanin <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, October 10, 2007 7:59:17 PM
Subject: Re: ivy fails to build from a fresh checkout
On 10/10/07, Adrian Woodhead <[EMAIL PROTECTED]> wrote:
I have just done a fresh checkout of ivy/core/trunk, made no changes
at
all and run
ant jar
and I get the following error:
[ivy:retrieve]
[ivy:retrieve] :: problems summary ::
[ivy:retrieve] :::: WARNINGS
[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-lang-[1.0,3.0[.pom
':
escaped absolute path not valid
[ivy:retrieve]
::::::::::::::::::::::::::::::::::::::::::::::
[ivy:retrieve]
[ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
If I modify the "rev" attribute on line 50 of ivy.xml from
rev="[1.0,3.0["
to
rev="1.0"
the build succeeds. Is it worth creating a Jira issue for this or can
someone just do this hopefully quick and easy fix?
The error has already been reported but it should be fixed:
https://issues.apache.org/jira/browse/IVY-390
So maybe you could reopen it with as many details as possible on your
environment (OS, Ant and Java version - Libraries in your classpath
like
httpclient).
Thanks.
Xavier
Adrian
