If I group it in a module like so:
<dependency org="nhibernate" name="nhibernate" rev="1.0.1.2">
<artifact name="a" ext="dll"/>
<artifact name="b" ext="dll"/>
<artifact name="c" ext="dll"/>
<artifact name="d" ext="dll"/>
</dependency>
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.
<dependency org="nhibernate" name="nhibernate" rev="1.0.1.2">
Gilles Scokart wrote:
>
> 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:[EMAIL PROTECTED]
>> Sent: mercredi 22 août 2007 10:23
>> To: [email protected]
>> Subject: RE: Dependency configuration scenario
>>
>>
>> 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
>>
>> 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?
>>
>> <?xml version="1.0" encoding="ISO-8859-1"?>
>> <?xml-stylesheet type="text/xsl"
>> href="http://www.jayasoft.fr/org/ivyrep/ivy-doc.xsl";?>
>> <ivy-module version="1.0">
>> <info
>> organisation="3rdparty"
>> module="nhibernate-full"
>> revision="1.0.2.0"
>> status="release">
>>
>> </info>
>> <dependencies>
>> <dependency org="3rdparty" name="nhibernate" rev="1.0.2.0">
>> <dependency org="3rdparty" name="Iesi.Collections" rev="1.0.2.0"/>
>> </dependency>
>> </dependencies>
>> </ivy-module>
>>
>> Thanks
>>
>>
>>
>>
>>
>> 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:[EMAIL PROTECTED]
>> >> Sent: mardi 21 août 2007 18:03
>> >> To: [email protected]
>> >> 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="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.
>> >
>> >
>> >
>>
>> --
>> 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.
>
>
>
--
View this message in context:
http://www.nabble.com/Dependency-configuration-scenario-tf4306123.html#a12274524
Sent from the ivy-user mailing list archive at Nabble.com.
