ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Archie Cobbs <>
Subject Re: conf mapping documentation contradicts itself
Date Tue, 04 May 2010 21:14:39 GMT
On Tue, May 4, 2010 at 4:01 PM, mjparme <> wrote:

> The reason the current verbiage of "master configuration (i.e. the
> configuration of the module defining the dependency)" is confusing because
> it reads like it is talking about the ivy file that defines the dependency.
> Whereas the first sentence defines master configuration as the ivy file of
> the current module.

Seems like there's still confusion about what the docs intended to mean...

The ivy file defining the dependency *is* the ivy file of the current
module. Here the word "dependency" is referring to a relationship between
two modules. So there are three things being defined here: two modules and a

The dependency is defined inside the "master" module's ivy.xml file. The
module being depended on is of course defined by it's ivy.xml file (i.e.,
the other ivy.xml file). So modules "know" what they depend on, but modules
don't "know" who depends on them.


Archie L. Cobbs

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