Return-Path: 
 <ivy-user-return-710-apmail-incubator-ivy-user-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org
Received: (qmail 64502 invoked from network); 18 Apr 2007 21:24:32 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 18 Apr 2007 21:24:32 -0000
Received: (qmail 10439 invoked by uid 500); 18 Apr 2007 21:24:38 -0000
Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org
Received: (qmail 10405 invoked by uid 500); 18 Apr 2007 21:24:38 -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 10396 invoked by uid 99); 18 Apr 2007 21:24:38 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Apr 2007 14:24:38 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: local policy)
Received: from [68.142.200.152] (HELO web30809.mail.mud.yahoo.com)
 (68.142.200.152)
    by apache.org (qpsmtpd/0.29) with SMTP; Wed, 18 Apr 2007 14:24:30 -0700
Received: (qmail 21856 invoked by uid 60001); 18 Apr 2007 21:24:10 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
  b=P29vBUghl2XjS3BhiCf2vPD4WC7LRG+yf4lJKKLC8CUhQYbnw5S68ZfwTyROhacR9K+msi8xO87NogQbmYpjcULJfCVxUUouJKOz9pRCpSCW63h2LsbmzvFqpHglyDpeEBZdge3pHYyKZ6GmI+bslyNdkWcYEiZnX0R5PpnLySE=;
X-YMail-OSG: 
 53TPc_AVM1mupr5VID74sf8qmz4OCwyVt8qsjxKoreiTBAymaZ6XZWT_GAc8P2UX9Q--
Received: from [209.191.106.127] by web30809.mail.mud.yahoo.com via HTTP;
 Wed, 18 Apr 2007 14:24:09 PDT
X-Mailer: YahooMailRC/651.14 YahooMailWebService/0.7.41.10
Date: Wed, 18 Apr 2007 14:24:09 -0700 (PDT)
From: Maarten Coene <maarten_coene@yahoo.com>
Subject: Re: compile, runtime and interface configuration
To: ivy-user@incubator.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ascii
Message-ID: <996911.21562.qm@web30809.mail.mud.yahoo.com>
X-Virus-Checked: Checked by ClamAV on apache.org

If I remember things correctly, here is how it works.

When Ivy parses your Ivy file, it will create (internally) modify the configuration mapping of your dependencies.
For instance, say you have:

<configurations defaultconfmapping="conf1->other1;conf2->other2">
    <conf name="conf1" />
    <conf name="conf2" extends="conf1" />
</configurations>
<dependencies>
    <dependency name="other-module" conf="conf1" />
</dependencies>

When Ivy parses this file, it will construct the following dependency (in-memory only):
    <dependency name="other-module" conf="conf1->other1" />


So, if you now resolve the conf2 configuration, you will only get the other1 dependencies of your other-module.

But here comes the confmappingoverride to the rescue ;-) When you set this attribute to true, Ivy will construct the following dependency in memory:
    <dependency name="other-module" conf="conf1->other1;conf2->other2" />
As you can see, the defaultmappings of the extending configurations are also added (although you didn't explicitly defined them)



When you now resolve the conf2 configuration, you'll get the other2 dependencies of your other-module.

I hope this helps you understanding the impact of this attribute

regards,
Maarten


----- Original Message ----
From: Gilles Scokart <gscokart@gmail.com>
To: ivy-user@incubator.apache.org
Sent: Wednesday, April 18, 2007 9:30:14 AM
Subject: RE: compile, runtime and interface configuration

Unfortunately, the thread is not available anymore.

Could you explain "the extending configurations will override the mappings
of the configurations they extend from".   Because for the moment I'm not
sure that "I understand the implications" ;-).


Thanks,
Gilles


> -----Original Message-----
> From: Maarten Coene [mailto:maarten_coene@yahoo.com]
> Sent: mercredi 18 avril 2007 9:01
> To: ivy-user@incubator.apache.org
> Subject: Re: compile, runtime and interface configuration
> 
> Gilles,
> 
> you have to set the confmappingoverride property to true to have this
> behaviour.
> See http://incubator.apache.org/ivy/doc/ivyfile/configurations.html
> 
> I think this will solve your problem...
> 
> regards,
> Maarten
> 
> ----- Original Message ----
> From: Gilles Scokart <gscokart@gmail.com>
> To: ivy-user@incubator.apache.org
> Sent: Wednesday, April 18, 2007 8:31:42 AM
> Subject: RE: compile, runtime and interface configuration
> 
> Ok, here is a simplified example:  A module 'User' depends on a module
> 'Service'.  The module 'service' use in its interface some classes of the
> module 'datatype', and use internally the module 'serviceImpl'
> 
> Module 'user' :
> <dependencies>
>     <dependency org="X" name="service" rev="x" conf="compile"/>
> </dependencies>
> 
> 
> Module 'service' :
> <dependencies>
>     <dependency org="X" name="datatype" rev="x" conf="interface"/>
>     <dependency org="X" name="serviceImpl" rev="x" conf="compile"/>
> </dependencies>
> 
> 
> 
> When I resolve the dependencies user, I would like to have
> - in conf compile : service , datatype
> - in conf runtime : service , datatype , serviceImpl
> 
> 
> However, with the configuration :
> <configurations
>     defaultconfmapping="runtime -> runtime(default);
>                         interface -> interface(default);
>                         compile -> interface(default)">
> 
>     <conf name="compile" extends="interface"/>
>     <conf name="runtime" extends="compile"/>
>     <conf name="interface"/>
> </configurations>
> 
> I think I have the configuration runtime containing only service and
> datatype.
> 
> 
> Gilles
> 
> 
> 
> > -----Original Message-----
> > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > Sent: mardi 17 avril 2007 17:28
> > To: ivy-user@incubator.apache.org
> > Subject: Re: compile, runtime and interface configuration
> >
> > On 4/17/07, Gilles Scokart <gscokart@gmail.com> wrote:
> > >
> > >
> > >
> > >
> > >
> > > Hi,
> >
> >
> > Hi,
> >
> > I try to to define a system that use three types of configurations :
> > > compile, runtime and interface.
> > >
> > >
> > >
> > > The compile dependencies are the one required to compile my modules.
> > >
> > > The runtime dependencies are the one required to run my modules.
> > >
> > > The interface dependencies are dependencies that I use in the
> interface
> > of
> > > my module.  The means that the users of my module should transitively
> > > inherit those interfaces in their compile (and runtime) dependencies.
> > >
> > >
> > >
> > >
> > >
> > > Here is how I tried to declare those configurations :
> > >
> > >
> > >
> > > <configurations  defaultconfmapping=" runtime -> runtime(default);
> > >
> > >                                       interface -> interface(default);
> > >
> > >                                       compile -> interface(default)">
> > >
> > >
> > >
> > >             <conf name="compile" extends="interface" description="the
> > > compile-time dependencies" />
> > >
> > >             <conf name="runtime" extends="compile " description="The
> > > runtime
> > > configuration"/>
> > >
> > >             <conf name="interface" description="The interface
> > > configuration"/>
> > >
> > > </configurations>
> > >
> > >
> > >
> > >
> > >
> > > When I have A depends in B (compile dep) and B depends on C (compile
> > dep),
> > > I
> > > was expecting to have implicitly A depends on C (runtime dep).  But it
> > > seems
> > > not to be.
> >
> >
> > Could you be more precise when you talk about your deps configurations
> > (giving the dependency element of each ivy file), because I'm not sure
> how
> > you use the defaultconfmapping you have defined.
> >
> > Xavier
> >
> > I have the impression that ivy first resolve the compile dependencies
> > > transitively, then resolve runtime dependencies transitively and add
> the
> > > one
> > > obtained by the compile dep resolution.
> >
> >
> >
> > Is my understanding correct?  What are the other alternative to do what
> I
> > > want to do?  Am I forced to flag all compile dependencies also as
> > runtime
> > > dependencies?
> > >
> > >
> > >
> > >
> > >
> > > Thanks for your help.
> > >
> > >
> > >
> > > Gilles
> > >
> > >
> > >
> > >
> >
> >
> > --
> > Learn Ivy at ApacheCon: http://www.eu.apachecon.com/
> > Manage your dependencies with Ivy!
> > http://incubator.apache.org/ivy/
> 
> 
> 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com





__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com