Return-Path: Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org Received: (qmail 97485 invoked from network); 22 Aug 2007 13:22:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Aug 2007 13:22:52 -0000 Received: (qmail 63049 invoked by uid 500); 22 Aug 2007 13:22:48 -0000 Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org Received: (qmail 63022 invoked by uid 500); 22 Aug 2007 13:22:48 -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 63010 invoked by uid 99); 22 Aug 2007 13:22:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2007 06:22:48 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2007 13:23:20 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1INqA9-0004f7-U6 for ivy-user@incubator.apache.org; Wed, 22 Aug 2007 06:22:21 -0700 Message-ID: <12274524.post@talk.nabble.com> Date: Wed, 22 Aug 2007 06:22:21 -0700 (PDT) From: mike gman To: ivy-user@incubator.apache.org Subject: RE: Dependency configuration scenario In-Reply-To: <009501c7e498$d4f44a50$0920a8c0@isabelteam.be> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Nabble-From: michaelg@osiristrading.com References: <12257674.post@talk.nabble.com> <008a01c7e48e$31cdd350$0920a8c0@isabelteam.be> <12270233.post@talk.nabble.com> <009501c7e498$d4f44a50$0920a8c0@isabelteam.be> X-Virus-Checked: Checked by ClamAV on apache.org If I group it in a module like so: When I reference it from a dependent project do i still need to specify the artifacts or will it automatically pull the dlls into the dependent project E.g from my dependent project. Gilles Scokart wrote: >=20 > I would advice to have one module per thing that has its own release > cycle. > If all your dll are always released together, then you don't really need > dependency management between them, and having one module is the right > approach. >=20 > Gilles >=20 >> -----Original Message----- >> From: mike gman [mailto:michaelg@osiristrading.com] >> Sent: mercredi 22 ao=C3=BBt 2007 10:23 >> To: ivy-user@incubator.apache.org >> Subject: RE: Dependency configuration scenario >>=20 >>=20 >> Question 1) >> So is it best practice to separate every single dll into its own >> configuration/folder? >> It is not a problem for me to do it this way. >> If I would like to create different modules groupings - what is the >> recommended method? >> E.g. Nhibernate-full-2.0 -> a.dll, b.dll, c.dll, d.ll, e.dll >> Nhibernate-basic-2.0 -> a.dll, b.dll >>=20 >> If I create separate modules (as above) the dependency resolver always >> looks >> for a file called "Hibernate-full-2.0". How can I tell it that the modul= e >> is >> just a shell for pointing to other dependencies? >>=20 >> >> > href=3D"http://www.jayasoft.fr/org/ivyrep/ivy-doc.xsl"?> >> >> > organisation=3D"3rdparty" >> module=3D"nhibernate-full" >> revision=3D"1.0.2.0" >> status=3D"release"> >>=20 >> >> >> >> >> >> >> >>=20 >> Thanks >>=20 >>=20 >>=20 >>=20 >>=20 >> Gilles Scokart wrote: >> > >> > What you can do is placing a.dll, b.dll, c.dll etc... as artefact in >> the >> > ivy.xml of the NHibernate module. >> > >> > Note that if you do that, you will not benefits of the dependency >> > management >> > (conflict resolution, version management, etc.) of your individual dll= . >> > You >> > might have problem if your application use an other module that also >> use >> > a, >> > b or c.dll. (But it is maybe not a problem in your case). >> > >> > Gilles >> > >> >> -----Original Message----- >> >> From: mike gman [mailto:michaelg@osiristrading.com] >> >> Sent: mardi 21 ao=C3=BBt 2007 18:03 >> >> To: ivy-user@incubator.apache.org >> >> Subject: Dependency configuration scenario >> >> >> >> >> >> I am trying to get the following setup to work: >> >> >> >> Example shared repository >> >> NHibernate folder -> contains a.dll, b.dll, c.dll etc.... >> >> >> >> I would like to reference NHibernate as a module which in turn >> references >> >> all its libraries (a,b,c etc) which happen to sit in the same folder. >> I >> >> don't want to create separate libraries/folders for a,b,c (too much >> >> work). >> >> >> >> My dependent project would contain an entry in the ivy.xml as below: >> >> >> >> Is it possible to reference a module like this that returns all the >> dlls >> >> in >> >> the folder. >> >> >> >> >> >> -- >> >> View this message in context: http://www.nabble.com/Dependency- >> >> configuration-scenario-tf4306123.html#a12257674 >> >> Sent from the ivy-user mailing list archive at Nabble.com. >> > >> > >> > >>=20 >> -- >> View this message in context: http://www.nabble.com/Dependency- >> configuration-scenario-tf4306123.html#a12270233 >> Sent from the ivy-user mailing list archive at Nabble.com. >=20 >=20 >=20 --=20 View this message in context: http://www.nabble.com/Dependency-configuratio= n-scenario-tf4306123.html#a12274524 Sent from the ivy-user mailing list archive at Nabble.com.