ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maarten Coene <maarten_co...@yahoo.com>
Subject Re: Can't resolve commons-daemon
Date Tue, 08 Mar 2011 14:34:04 GMT
You get this because the POM of commons-daemon is not correct.
It contains the following:

<groupId>org.apache.commons</groupId>
<artifactId>commons-daemon</artifactId>

However, according to the URL, it should be:

<groupId>commons-daemon</groupId>
<artifactId>commons-daemon</artifactId>

You can disable this check in Ivy by adding setting the 'checkconsistency' attribute to false
on your ibiblio resolver.

<ivysettings>
...
     <ibiblio name="ibiblio" checkconsistency="false"/> 

</ivysettings>


regards,

Maarten




----- Original Message -----
From:Filipe Sousa <natros@gmail.com>
To:ivy-user@ant.apache.org
Cc:
Sent:Tuesday, March 8, 2011 1:12 PM
Subject:Can't resolve commons-daemon

Hi,
I want to do some experiments with commons-daemon, but I am having a
problem. Ivy can't resolve the next dependency
<dependency org="commons-daemon" name="commons-daemon" rev="1.0.3" />

gives me the following error:

ivy:retrieve] :::: WARNINGS
[ivy:retrieve]          ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:retrieve]          ::          UNRESOLVED DEPENDENCIES         ::
[ivy:retrieve]          ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:retrieve]          :: commons-daemon#commons-daemon;1.0.3:
java.text.ParseException: inconsistent module descriptor file found in
'http://repo1.maven.org/maven2/commons-daemon/commons-daemon/1.0.3/commons-daemon-1.0.3.pom':
bad organisation: expected='commons-daemon'
found='org.apache.commons';
[ivy:retrieve]          ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:retrieve] :::: ERRORS
[ivy:retrieve]          ibiblio: bad organisation found in
http://repo1.maven.org/maven2/commons-daemon/commons-daemon/1.0.3/commons-daemon-1.0.3.pom:
expected='commons-daemon' found='org.apache.commons'
[ivy:retrieve]
[ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS

I asked in the apache commons mailing list and they think this can be
a ivy problem.
-- 
Filipe Sousa



      

Mime
View raw message