ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Louis Boudart <>
Subject Re: Extending Ivy Files
Date Wed, 22 Jun 2011 08:57:12 GMT
Hi Mark,

Extends mechanism tries first to check on filesystem to find the parent
module descriptor (../ivy.xml by default but can be specified through
location attribute on extends tag). If found it checks that it matches with
organisation / module information from extends tag.
If not found it tries to resolve it using all defined repositories.

Then problem comes when you try to publish as ivy tries to parse the module
descriptor from the cache, if your module descriptor uses "extends" feature
it will check first parent descriptor on file system (../ivy.xml by
default). That's why you have this strange warning.
Extends mechanism has been strongly improved on trunk, and this kind of
problem should not happened now, could you please give a try with a nightly
build ?

extendType attribute is used to "limit" what you want to be inherited *info*,
*description*, *configurations*, *dependencies*, and *all* (default is all).


2011/6/16 Mark R Maxey <>

> Can anyone point me to a working example of where one Ivy file extends from
> another?  I've tried, but am stumped.
> I have 3 Ivy files:
>      ivy.xml: organisation="foo" module="bar" - I use this to retrieve
>      stuff from keystone#schema
>      ivy-bar.xml:  organisation="keystone" module="schema" - This uses
>      info's "extends" element to include keystone#conf
>      ivy-conf.xml: organisation="keystone" module="conf"
> I keep getting the error (my cache is located in /some/path/cache):
> WARN: Unable to parse included ivy
> file ../ivy.xml: /some/path/cache/org/ivy.xml (No such file or directory)
> in file:/some/path/cache/org/ivy.xml
> Without using info's "extends" element, everything works fine.
> This confuses me for many reasons:
>      I don't use relative paths anywhere, i.e., I don't use "../" to
>      reference anything.
>      I don't have any files that rely on loading "ivy.xml".  I can start
>      and run much of the retrieve target fine, so ivy.xml is valid.  If I
>      use extends "location" attribute and specify "ivy-conf.xml" directly,
>      then I get almost the same error, just with "ivy.xml" replaced by
>      "ivy-conf.xml".
>      /some/path/cache/org/ivy.xml really doesn't exist and never will.
>      I'm not sure why it is looking there.
> I've tried setting extendType="configurations", but it had no affect.
> Any ideas?
> Thanks!
> Mark Maxey

Jean Louis Boudart
Independent consultant
Project Lead

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