Return-Path: 
 <ivy-user-return-1138-apmail-incubator-ivy-user-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org
Received: (qmail 19843 invoked from network); 28 Jun 2007 20:08:22 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 28 Jun 2007 20:08:22 -0000
Received: (qmail 60916 invoked by uid 500); 28 Jun 2007 20:08:25 -0000
Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org
Received: (qmail 60886 invoked by uid 500); 28 Jun 2007 20:08:25 -0000
Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@incubator.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@incubator.apache.org>
List-Post: <mailto:ivy-user@incubator.apache.org>
List-Id: <ivy-user.incubator.apache.org>
Reply-To: ivy-user@incubator.apache.org
Delivered-To: mailing list ivy-user@incubator.apache.org
Received: (qmail 60877 invoked by uid 99); 28 Jun 2007 20:08:25 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jun 2007 13:08:25 -0700
X-ASF-Spam-Status: No, hits=2.0 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of xavier.hanin@gmail.com
 designates 64.233.184.228 as permitted sender)
Received: from [64.233.184.228] (HELO wr-out-0506.google.com) (64.233.184.228)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jun 2007 13:08:19 -0700
Received: by wr-out-0506.google.com with SMTP id i22so538863wra
        for <ivy-user@incubator.apache.org>;
 Thu, 28 Jun 2007 13:07:59 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=ZeXwwzufRutZRtRy7blpkLfZpeUJdF5gNsjp3YBZkXwDrZoyecDsQxHEZPmMQhksxZz7ks+kO5P7Ob5VUYP6zvBg+sZ040E9LHBTFwu1MkxFYi5Sm0DyPjXYRS4xCnpK8m62i5wqHUXlWCq0vyn6ab81pPBH7Gnm2FXCwH8Ylpk=
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:references;
        b=XnR/hiUWaHxI1DaZejmNjbqCgPYU5qR0w0bbBTOqVUIeMvQwi3NnZAb8x5HepLt0GDytUXuZoA5ThHhYNzwzFemnrDQylTf8MPbQOy9UyYwf1CVPpE79H+mCrYuhtH1u6Wg+FhiNC8DEaFGUwfYhwFCjNzXiHvTzHl3Oxv3jNpY=
Received: by 10.115.55.1 with SMTP id h1mr1887772wak.1183061277276;
        Thu, 28 Jun 2007 13:07:57 -0700 (PDT)
Received: by 10.114.124.10 with HTTP; Thu, 28 Jun 2007 13:07:57 -0700 (PDT)
Message-ID: <635a05060706281307u3b3af41eucaeb9defbf355f74@mail.gmail.com>
Date: Thu, 28 Jun 2007 22:07:57 +0200
From: "Xavier Hanin" <xavier.hanin@gmail.com>
To: ivy-user@incubator.apache.org
Subject: Re: dynamic resolution against proxy
In-Reply-To: <20070628141420.48kbofcqqsc408gg@www2.digizenstudio.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_58987_4356219.1183061277246"
References: <20070628141420.48kbofcqqsc408gg@www2.digizenstudio.com>
X-Virus-Checked: Checked by ClamAV on apache.org

------=_Part_58987_4356219.1183061277246
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 6/28/07, Jing Xue <jingxue@digizenstudio.com> wrote:
>
>
>
> Hi,
>
> I'm trying to build ivy against a maven-proxy (which runs in jetty). I
> changed the ivysettings.xml to use:
> <ibiblio name="public" root="http://myproxyserver/repository/"
> m2compatible="true"/>
>
> And I got an internal server error:
> [ivy:retrieve]  SERVER ERROR: Internal Server Error
> url=
> http://myproxyserver/repository/commons-lang/commons-lang/[1.0,3.0[/commons-lang-[1.0,3.0[.pom
>
> The internal server error itself isn't the point of this email,
> because that's jetty's problem - and in turn mine. 8-)  My question
> here is, does it actually make sense for ivy to actually request this
> pom, knowing it can't really exist.


Since Ivy does not mandate anything about revision names, it always check
the exact revision you ask before evaluating it as a constraint. Fortunately
you can disable that, using alwaysCheckExactRevision="false" on your
resolver.

I wonder if it wouldn't be interesting to change the default value of this
attribute in 2.0, since I think that very few people actually benefit from
it.

WDYT?

Xavier

--
> Jing Xue
>
>
>


-- 
Xavier Hanin - Independent Java Consultant
Creator of Ivy, xooki and xoocode.org
More about me: http://xhab.blogspot.com/

------=_Part_58987_4356219.1183061277246--