Return-Path: 
 <ivy-user-return-5159-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: (qmail 55632 invoked from network); 24 Apr 2009 07:33:21 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 24 Apr 2009 07:33:21 -0000
Received: (qmail 89635 invoked by uid 500); 24 Apr 2009 07:33:20 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 89587 invoked by uid 500); 24 Apr 2009 07:33:20 -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 89577 invoked by uid 99); 24 Apr 2009 07:33:20 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Apr 2009 07:33:20 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy)
Received: from [64.6.254.129] (HELO tbee.org) (64.6.254.129)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Apr 2009 07:33:10 +0000
Received: (qmail 26241 invoked from network); 24 Apr 2009 03:32:49 -0400
Received: from 82-169-203-130.ip.telfort.nl (HELO ?127.0.0.1?)
 (82.169.203.130)
  by tbee.org with SMTP; 24 Apr 2009 03:32:49 -0400
Message-ID: <49F16B1F.1030005@tbee.org>
Date: Fri, 24 Apr 2009 09:32:47 +0200
From: Tom <tbee@tbee.org>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: ivy-user@ant.apache.org
Subject: Re: Configurations and Ivy file confusion
References: <d7681c140904211619g5b173639pac0c7b278e6cdb21@mail.gmail.com>
	 <d7681c140904220651q6c5d7423i4e77561b9c1913d7@mail.gmail.com>
	 <49EF238A.5020908@tbee.org>
 <d7681c140904220721j22972ed7k5968ae205e72135d@mail.gmail.com>
 <49EF2CA8.2080907@tbee.org> <49EF3982.2040301@masergy.com>
 <49EF4F77.4070005@tbee.org> <49EF5D80.1080201@masergy.com>
 <49F00D7D.4010508@tbee.org> <49F070DB.6070301@masergy.com>
In-Reply-To: <49F070DB.6070301@masergy.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiVirus: checked (outgoing) by AntiVir MailGuard (Version: 9.0.0.6;
 AVE: 8.2.0.155; VDF: 7.1.3.102)
X-Virus-Checked: Checked by ClamAV on apache.org


>> Appearantly I did something wrong. Running "ivy:retrieve" now downloads
>> 94 jars. Ok. However, if I I now want to split up like this:
>>
>> <ivy:retrieve conf="runtime" pattern="lib/[artifact]-[revision].[ext]"/>
>> <ivy:retrieve conf="test" 
>> pattern="lib-test/[artifact]-[revision].[ext]"/>
>> <ivy:retrieve conf="build" 
>> pattern="lib-ext/[artifact]-[revision].[ext]"/>
>>
>> Then I get an error
>>
>> /BUILD FAILED
>> C:\Documents and Settings\User\My
>> Documents\kpprofiler2\components\service\build.xml:39: impossible to ivy
>> retrieve: java.lang.RuntimeException: problem during
>> retrieve of nl.knowledgeplaza#kpprofiler-service:
>> java.lang.RuntimeException: Multiple artifacts of the module
>> org.codehaus.enunciate#enunciate-rt;1.10 are ret
>> ieved to the same file! Update the retrieve pattern to fix this error.
>> /
>
> OK, many projects have source and jar artifacts with the same name, so 
> you really want to either set a retrieve pattern which includes the 
> type of the artifact for disambiguation. If you cannot do this, you'll 
> need to specify an exclusion rule for your dependencies to only 
> include type jar. Here are examples of both:
>
>         <ivy:retrieve 
> pattern="${ivy.lib.dir}/[type]/[artifact]-[revision].[ext]" 
> haltonfailure="true" conf="build" sync="true"/>
>
>         <dependencies>
>           <exclude type="source"/>
>         </dependencies>
>

Hm. Ok, I understand the problem that if multiple artifact are 
downloaded to the same file, then that would be an error. But why does 
"<ivy:retrieve/>" not have the same problem? Logically again; I have 4 
dependency lines resulting in 94 jars, and the only thing I can do is 
filter these jars using configuration labels, how does limiting these 94 
jars introduce a retrieved-to-same-file exception? If the error doesn't 
occur in the 94, how can it occur in a subset?

Tom