Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of gscokart@gmail.com designates
 209.85.128.187 as permitted sender)
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:in-reply-to:x-mimeole:thread-index;
        b=B7nnCmktdo7JeOa01rVUlM/LIdRkuo6tgDIaou2Bi1pO8arMYLTfmdVXuPxxn/x/GFqjKVW8cWsNL29lFD4rZO4ikbPocBMv8sArwLz7HTLh33jbZ4HAi5J6mpr5dLMeVlTbC6C1stDTAVfHvDvGSUIVhuH2YkwTctm4dxtprog=
From: "Gilles Scokart" <gscokart@gmail.com>
To: <ivy-user@incubator.apache.org>
Subject: RE: Dependency configuration scenario
Date: Wed, 22 Aug 2007 10:45:43 +0200
Message-ID: <009501c7e498$d4f44a50$0920a8c0@isabelteam.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <12270233.post@talk.nabble.com>
thread-index: AcfklahoP9GpZwt5R7u0JPXD9IJfiAAAo5zg

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.

Gilles

> -----Original Message-----
> From: mike gman [mailto:michaelg@osiristrading.com]
> Sent: mercredi 22 ao=FBt 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 =
module
> is
> just a shell for pointing to other dependencies?
>=20
> <?xml version=3D"1.0" encoding=3D"ISO-8859-1"?>
> <?xml-stylesheet type=3D"text/xsl"
> href=3D"http://www.jayasoft.fr/org/ivyrep/ivy-doc.xsl"?>
> <ivy-module version=3D"1.0">
>     <info
>         organisation=3D"3rdparty"
>         module=3D"nhibernate-full"
>         revision=3D"1.0.2.0"
>         status=3D"release">
>=20
>     </info>
>    <dependencies>
>       <dependency org=3D"3rdparty" name=3D"nhibernate" =
rev=3D"1.0.2.0">
>      <dependency org=3D"3rdparty" name=3D"Iesi.Collections" =
rev=3D"1.0.2.0"/>
>    </dependency>
>   </dependencies>
> </ivy-module>
>=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=FBt 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:
> >> <dependency org=3D"3rdparty" name=3D"NHibernate" rev=3D"1.0.2.0">
> >> 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.