Return-Path: 
 <ivy-user-return-5146-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: (qmail 60315 invoked from network); 22 Apr 2009 17:40:56 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 22 Apr 2009 17:40:56 -0000
Received: (qmail 93780 invoked by uid 500); 22 Apr 2009 17:40:56 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 93759 invoked by uid 500); 22 Apr 2009 17:40:56 -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 93749 invoked by uid 99); 22 Apr 2009 17:40:56 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Apr 2009 17:40:56 +0000
X-ASF-Spam-Status: No, hits=2.2 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of archie.cobbs@gmail.com
 designates 74.125.46.157 as permitted sender)
Received: from [74.125.46.157] (HELO yw-out-1718.google.com) (74.125.46.157)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Apr 2009 17:40:49 +0000
Received: by yw-out-1718.google.com with SMTP id 6so56075ywa.70
        for <ivy-user@ant.apache.org>; Wed, 22 Apr 2009 10:40:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:content-type;
        bh=owrhhpK7tpRDiLxu9OCW6Bf9WsWoUKKaAnhoZimr0no=;
        b=pkmCcWIZRBnMZ/OALSkadoCcFpHIqAW+Q1s61STr1ioF5vA8jmOiBG8lnU15P3FoxQ
         B7T6EN2/VgX1fYlXXWxaYeFNuMbW/X0V7+6AOWiAyT31nJa9rpwkm+X1KnXRAnwGzbJJ
         y5YrYUf+D5uuJAxq48hTtLPqTjHz/FZrqhEok=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=S8TfnlUZ3YDsZ3wMjeReb920PaWeGxpNc76zA6nALq6uSpU8jGGmLACh2K+FY6EJuK
         CMBxSwkPdcmbIUwBVyp4nFFrO2cbKdj56VJvg+u3UGoZa6Y9VjvOgYAzU99l1yGgUlzW
         wJiOvx7CHqX5wsgneOvYpHupWknJZn5Tld/w0=
MIME-Version: 1.0
Received: by 10.100.232.15 with SMTP id e15mr11726423anh.129.1240422028602;
	Wed, 22 Apr 2009 10:40:28 -0700 (PDT)
In-Reply-To: <49EF4F77.4070005@tbee.org>
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>
Date: Wed, 22 Apr 2009 12:40:28 -0500
Message-ID: <3bc8237c0904221040q71960f18kdab7b80e7b7aa71a@mail.gmail.com>
Subject: Re: Configurations and Ivy file confusion
From: Archie Cobbs <archie.cobbs@gmail.com>
To: ivy-user@ant.apache.org
Content-Type: multipart/alternative; boundary=0016368e1fab62f2c90468284272
X-Virus-Checked: Checked by ClamAV on apache.org

--0016368e1fab62f2c90468284272
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Think of it this way:

Rule #1: A configuration is just a name for some subset of a module's
artifacts.

Rule #2: A dependency defind in module A's ivy.xml that looks like:

        <dependency name="B" conf="foo->bar"/>

simply states that "when someone is asking for the artifacts in
configuration 'foo' of module A, then we'll also need the artifacts in
configuration 'bar' of module B".

Hope that helps.

-Archie

On Wed, Apr 22, 2009 at 12:10 PM, Tom <tbee@tbee.org> wrote:

>
>  In this case, you're relying on Ivy's default configuration mapping, which
>> I believe is "*->*", which means you'll get all of the artifacts (jars)
>> defined by *any* of the dependency's configurations.
>>
>
> Ok. I do not understand what that means, but ok.
>
>
>  Now you have limited the artifacts to those defined by the "default"
>> configuration of each dependency. That probably doesn't include jars from
>> configs like "test", "sources", etc.
>>
>
> I have tried "runtime->*" but that did not change anything.
>
>
>
>  Configuration mapping has been the most confusing part of Ivy for me. I
>> still haven't mastered the use of it to come up with a best practices within
>> our organization.
>>
>
> May I put on the table that if a feature is this complicated to use, that
> maybe there is a flaw in the underlying concept? I still do not understand
> what configurations are trying to do. Are they:
> - trying to bind dependencies to usages? (The dependency is used within the
> scope "test", or "runtime", as I'm trying to do now)
> - trying to bind dependencies to deliverables? (For the deliverable
> "xyz.jar", use dependencies...)
>
> I also did not find a concept of "configuration" in Maven. Let's look at
> this from a simplistic approach:
> 1. my four dependency lines are resolved by Ivy to a list of 93 jars.
> 2. the only thing I can do with this list is limited / filter, I cannot
> expand it any further
> 3. so appearantly the configuration allows applying a filter to this list
> 4. you must filter on some attribute that is assigned to each jar... where
> would that assignment take place?
> 5. the jar itself could have that attribute set, but the developer can't
> know for what the jar is used.
> 6. the only logical place to assign a value would be in de ivy.xml in the
> project using it, inheriting from the initial line
>
> Where am I going wrong?
>
>
>
>
>


-- 
Archie L. Cobbs

--0016368e1fab62f2c90468284272--