ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles Scokart" <>
Subject RE: Dependency configuration scenario
Date Wed, 22 Aug 2007 07:29:35 GMT
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).


> -----Original Message-----
> From: mike gman []
> Sent: mardi 21 août 2007 18:03
> To:
> 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="3rdparty" name="NHibernate" rev="">
> Is it possible to reference a module like this that returns all the dlls
> in
> the folder.
> --
> View this message in context:
> configuration-scenario-tf4306123.html#a12257674
> Sent from the ivy-user mailing list archive at

View raw message