Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of gscokart@gmail.com designates
 64.233.162.230 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=U+/EDxE5wfEPnb5Gr0B75dBau34Xgftj569AG7TlEyUNdOq+HO74sZ8zC6D0tUDbIiQqpJwVITuwjrKcrvDKixLZKUet6c8hIS3lGrj/17xoH7wTMjRWpbuz8WEpclW8Znn1CJVBMwGMbF56JYNIfPO2G8g/9TV3chEszRG+HCk=
Message-ID: <e9d8a2610705271137j7704d1w18b09b2badf202ea@mail.gmail.com>
Date: Sun, 27 May 2007 20:37:59 +0200
From: "Gilles Scokart" <gscokart@gmail.com>
To: ivy-user@incubator.apache.org
Subject: Re: Dealing with bad POMs?
In-Reply-To: <10807248.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <10807248.post@talk.nabble.com>

I guess the best thing to do is to raise an issue in
http://jira.codehaus.org/browse/MEV as described there :
http://maven.apache.org/guides/mini/guide-maven-evangelism.html .  The
thing you describe are clearly errors in the repository.

As a workaround, you can may try to use an other repository where you
can install the correct poms (or ivy.xml files).  Maybe using a dual
resolver.

Note also that ivy can work with a repository without pom.xml nor
ivy.xml when the modules have no dependencies.

I hope it helps.

Gilles

2007/5/25, nirvdrum <kmenard@servprise.com>:
>
> Hi,
>
> As noted earlier, I'm looking to move from maven2 over to ant+ivy.  During
> the migration, I've run across problems with a few POMs on ibiblio.  maven2
> apparently deals with the problems okay, since I never had problems
> downloading the files.  ivy doesn't seem to allow me to. Is there anyway to
> tell ivy to download the files no matter what?
>
> As an example of the problems, one POM marks a version as 4.0.1, while the
> artifact is actually at version 4.0.2.  ivy finds the files in the correct
> path, but then compares against the POM and borks when the versions don't
> match.
>
> In another, the organization defined in the POM does not match that used as
> the path to the artifact.  Once again, ivy finds the file fine, but borks
> when doing a consistency check on the POM.
>
> Any help would be much appreciated.
>
> Thanks,
> Kevin
> --
> View this message in context: http://www.nabble.com/Dealing-with-bad-POMs--tf3817428.html#a10807248
> Sent from the ivy-user mailing list archive at Nabble.com.
>
>


-- 
Gilles SCOKART