From ivy-user-return-704-apmail-incubator-ivy-user-archive=incubator.apache.org@incubator.apache.org Wed Apr 18 06:32:28 2007 Return-Path: Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org Received: (qmail 69793 invoked from network); 18 Apr 2007 06:32:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Apr 2007 06:32:27 -0000 Received: (qmail 11709 invoked by uid 500); 18 Apr 2007 06:32:33 -0000 Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org Received: (qmail 11681 invoked by uid 500); 18 Apr 2007 06:32:33 -0000 Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@incubator.apache.org Delivered-To: mailing list ivy-user@incubator.apache.org Received: (qmail 11669 invoked by uid 99); 18 Apr 2007 06:32:32 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Apr 2007 23:32:32 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of gscokart@gmail.com designates 66.249.92.171 as permitted sender) Received: from [66.249.92.171] (HELO ug-out-1314.google.com) (66.249.92.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Apr 2007 23:32:25 -0700 Received: by ug-out-1314.google.com with SMTP id y2so352452uge for ; Tue, 17 Apr 2007 23:32:04 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:x-mimeole:in-reply-to:thread-index; b=PRUpIE+BJABZavqfnoOnDSZahJljBKOcHhD9Y8mPC3e8x7xhM3pxY9kIenmZcp+XZVskYH9IKLs1mX0LAUbQICyA+ENPcpRlVnEKdbGhewwibZfGfCJfY18Ypm3L7kSdEXM421G4PHOiCytjO4/AeYxvTl4weDPfowSvDmRlikM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:x-mimeole:in-reply-to:thread-index; b=AIMwoYFKbjG20oV/+0RuxgUpzRWzPJ5FomRqkaGaMTnQwVQkR2hT8W+MawyYmrbnlZCktuCr20oNOWDMbi/PzG2yvgB8spgKjYoAQ87c5XWzU9+8ih4ig7nMWPDYF6HPmT0bkdNgk4DGzp2xnbCZblzIDWYViuM9o0lkTADfTII= Received: by 10.66.243.2 with SMTP id q2mr1068762ugh.1176877924614; Tue, 17 Apr 2007 23:32:04 -0700 (PDT) Received: from SCOKARTGXP ( [195.122.110.8]) by mx.google.com with ESMTP id 53sm1460482ugd.2007.04.17.23.32.02; Tue, 17 Apr 2007 23:32:03 -0700 (PDT) From: "Gilles Scokart" To: Subject: RE: compile, runtime and interface configuration Date: Wed, 18 Apr 2007 08:31:42 +0200 Message-ID: <00c601c78183$3b8f3b90$2120a8c0@isabelteam.be> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 In-Reply-To: <635a05060704170828n60e04fbeuda19a7df71761657@mail.gmail.com> Thread-Index: AceBBRruZC0OCUKgTLmh64SdcqzrVAAfIAAQ X-Virus-Checked: Checked by ClamAV on apache.org 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' : Module 'service' : 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 : 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 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 : > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 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/