Return-Path: 
 <ivy-user-return-2412-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: (qmail 85368 invoked from network); 7 Feb 2008 00:33:29 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 7 Feb 2008 00:33:29 -0000
Received: (qmail 17127 invoked by uid 500); 7 Feb 2008 00:33:21 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 17080 invoked by uid 500); 7 Feb 2008 00:33:21 -0000
Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@ant.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@ant.apache.org>
List-Post: <mailto:ivy-user@ant.apache.org>
List-Id: <ivy-user.ant.apache.org>
Reply-To: ivy-user@ant.apache.org
Delivered-To: mailing list ivy-user@ant.apache.org
Received: (qmail 17066 invoked by uid 99); 7 Feb 2008 00:33:21 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Feb 2008 16:33:21 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of dbenua@panix.com designates
 166.84.1.74 as permitted sender)
Received: from [166.84.1.74] (HELO mail3.panix.com) (166.84.1.74)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Feb 2008 00:33:04 +0000
Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89])
	by mail3.panix.com (Postfix) with ESMTP id B61B113A869
	for <ivy-user@ant.apache.org>; Wed,  6 Feb 2008 19:32:57 -0500 (EST)
Received: from [192.168.1.100] (c-66-30-33-36.hsd1.ma.comcast.net
 [66.30.33.36])
	by mailbackend.panix.com (Postfix) with ESMTP id 93144123B9
	for <ivy-user@ant.apache.org>; Wed,  6 Feb 2008 19:32:57 -0500 (EST)
Message-ID: <47AA51B6.20808@panix.com>
Date: Wed, 06 Feb 2008 19:32:54 -0500
From: David Benua <dbenua@panix.com>
Reply-To: dbenua@panix.com
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: ivy-user@ant.apache.org
Subject: Re: Configuration from remote repositories
References: <47AA27DE.1040705@panix.com>
 <635a05060802061353w6a70c9aerd49a4d1dcaa2fc46@mail.gmail.com>
In-Reply-To: <635a05060802061353w6a70c9aerd49a4d1dcaa2fc46@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Xavier,

Thanks for the quick turnaround on this.

I've tried it, and as you said, it works (even if it's not documented). 
Here are the settings (so far) in the remote directory:

<ivysettings>
    <property name="repo.path" value="/home/ivyrep/repo" />
    <resolvers>
       <url name="local-http" >
          <ivy 
pattern="${ivy.settings.dir}/[organization]/[module]-ivy-[revision].xml" />
          <artifact 
pattern="${ivy.settings.dir}/[organization]/[module]/[revision]/[artifact]-[revision].[ext]" 
/>
          <artifact 
pattern="${ivy.settings.dir}/[organization]/[module]/[revision]/[artifact].[ext]" 
/>
       </url>
       <sftp name="local-sftp" host="${ivyrepo.host}" 
port="${ivyrepo.port}" user="${ivyrepo.user}" 
userPassword="${ivyrepo.password}" >
          <ivy 
pattern="${repo.path}/[organization]/[module]-ivy-[revision].xml" />

          <artifact 
pattern="${repo.path}/[organization]/[module]/[revision]/[artifact]-[revision].[ext]" 
/>
          <artifact 
pattern="${repo.path}/[organization]/[module]/[revision]/[artifact].[ext]" 
/>
       </sftp>
     </resolvers>
</ivysettings>

I've been able to retrieve with both resolvers. I'm sure that I'll have 
to add more options once we get going for real.  I expect we'll need to 
have integration (SNAPSHOT) builds, and separate configurations for 
building and testing, so I'm sure this will evolve before we're fully 
running.

> 
>      (I've also tried specifying
>     the settings file url in the <settings> or <configure> node, and that
>     doesn't work properly: it still looks for ivysettings.xml in my local
>     directory)
> 
> This is strange and is clearly a bug. Could you open an issue with more 
> details about what you tried?

All I tried was specifying an HTTP url in the <settings> tag.  Thinking 
about it now, it's not something that really would have helped: we're 
going to need some local configuration options, and this approach would 
not have worked.

Dave