ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Louis BOUDART <>
Subject Re: /ivy-module/dependencies/include exists?
Date Wed, 25 Feb 2009 10:14:42 GMT
As far as i know this feature is not yet implemented but there is an open
issue related to this

I've made a small patch as a POC that allow you to extends ivy files.

<extends organisation="foobar" module="child"
revision="latest.integration" location="../ivy.xml"

 Location defines where ivy should look on filesystem before asking
repository. This attribute is not mandatory. By default this attribute is
set to "../ivy.xml"

extendType attribute defines what you want to include. This is not a
mandatory attribute.
possible values for extendType :

   - all
   - configurations
   - dependencies
   - description

But what will happen when we publish/deliver such an ivy.xml file? Will we
publish/deliver it with the extends element in it, or will we
publish/deliver the merged result?

Currently the patch publish with the extends element in it :/
Publishing merged metadata is much cleaner and safer.  That's why this is
not yet included in ivy.

I hope i will have time work on it soon.


2009/2/24 Tim Julien <>

> in ivy.xml, I would like to be able to share dependencies across several
> internal modules.  For example, they all use, say, commons-logging and
> guice.  I don't want to have to configure, for example, the 'rev' in n
> different places.  I want to specify the version in one place and have them
> all use that version.
> The solution I am using now is to put the versions for various 3rd party
> libs in a properties file, and using <properties> in my ivy settings file.
> But I would love to be able to <include> an external <dependency> file,
> much like I am currently <include>'ing a <configuration> file which
> specifies the various <conf>s and 'defaultconfmapping'.
> Please reply to me, I am not subscribed to this list.
> thx!
> -Tim Julien

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message